digital-asset/daml
1
1
Fork 0
mirror of https://github.com/digital-asset/daml.git synced 2024-09-20 09:17:43 +03:00
Code Issues Projects Releases Wiki Activity
6993232593
daml/3rdparty
History
Leonid Shlyapnikov c7b5482e43 JWT HMAC256 Authorization (#2389) 
* Starting //ledger-service/jwt module

adding //3rdparty/jvm/com/auth0:java_jwt dependency, there are Scala JWT
libraries, however they are either immature or unsupported

* Keys and JWT generator utility/wrapper, WIP

* Keys and JWT generator utility/wrapper, WIP

* RSA Keys generator

* HMAC token validation added to command/create endpoint

HMAC is actually not good, need RSA, this is a shortcut for DABL team.

* Renaming

* command/create test cases fixed to pass OAth2 Bearer token

* removing unused method

* JWT authorization for /command/exercise

* the rest of the endpoints uses JWT authorization

removed hardcoded JwtPayload

* cleanup

* cleanup

* http status code in the header and in the json body should match now

* NotFound would also return a json body now

* Removing hardcoded JWT in the integration test

it is generated using the JwtSigner.HMAC256

* cleanup

* fixing error message

* instructions for making a JWT HMAC token for dev
2019-08-07 16:26:26 +00:00
..
c Enforce consistent formatting of BUILD files. (#412) 2019-04-12 13:10:16 +02:00
haskell New template desugaring (#2178) 2019-07-30 19:49:33 -04:00
jvm JWT HMAC256 Authorization (#2389) 2019-08-07 16:26:26 +00:00
BUILD open-sourcing daml 2019-04-04 09:33:38 +01:00
dependencies.digest JWT HMAC256 Authorization (#2389) 2019-08-07 16:26:26 +00:00
NO_AUTO_COPYRIGHT open-sourcing daml 2019-04-04 09:33:38 +01:00
README.md open-sourcing daml 2019-04-04 09:33:38 +01:00
workspace.bzl JWT HMAC256 Authorization (#2389) 2019-08-07 16:26:26 +00:00

README.md

Third-Party JVM Dependencies

This subtree contains a Bazel workspace file workspace.bzl and BUILD files underneath jvm/ describing external Java and Scala dependencies. These files are automatically generated and should not be modified manually. If you need to add a third party dependency then modify the file dependencies.yaml in the repository root and re-run bazel-deps in order to regenerate these files as described at the top of the file dependencies.yaml.

Third-Party Haskell Dependencies

The haskell/ subtree contains BUILD files defining custom Hazel builds for Cabal packages imported via Hazel's hazel_custom_package_* rules in the WORKSPACE.