-
Are there plans for Pivotal to implement any of the following IETF RFCs:
- RFC 7009 -- The OAuth 2.0 Token Revocation
- RFC 7521 -- Assertion Framework for OAuth 2.0 Client Authentication and Authoriz…
-
Hi,
Actually, the JWT token is serve in the HEADER response.
It would be better, to serve JWT Token in the body, like follow :
```php
{
"token" : "eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXUyJ9.e…
-
At the moment, consumers of our web services should provide an `Authorization` header on their request, containing nothing more but the Dicoogle session token. According to [RFC2617](http://www.ietf.o…
Enet4 updated
3 years ago
-
When decoding the JWT header, the input is converted `Map` using string operations. This simple parser fails with an `ArrayIndexOutOfBoundsException` if the header value contains a comma.
The JWT hea…
-
` [Docs] [txt|pdf] [draft-ietf-oaut...] [Tracker] [Diff1] [Diff2] [IPR] [Errata]
…
-
Engine service (**ENG**) should support authorisation over **JWT** mechanism ([RFC-7519](https://tools.ietf.org/html/rfc7519)).
A _JWT_ token should include at least _clientID_ to distiguish client…
-
**Describe the bug**
There is no "typ": "JWT" in header
**To Reproduce**
Try to use RESTClient with @JwtConfig for application secured by "MP-JWT"
**Expected behavior**
JwtBuilder should add …
-
### Summary
RFC 7519 section 6.1 specifies Unsecured JWTs with algorithm `none`:
https://www.rfc-editor.org/rfc/rfc7519#section-6
### Steps to reproduce
Try encoding using algorithm `none`:
```…
-
While attempting to follow a [short example](https://medium.com/@thegiraffeclub/jwks-authentication-with-micronaut-bf28845d3b61) on using JWKS based JWT auth, I ran into this error:
```
21:11:05.0…
-
The DURI Passport group is working on a new version of the GA4GH Passport specification that will define a new type of token for Passport following [RFC 8693 OAuth 2.0 Token Exchange](https://datatrac…