Teddy J. Torres
Teddy J. Torres
Hi @arjantijms, Please let us know if this challenge has been accepted or if more information is needed. Regards, Teddy
Hi @arjantijms, Please let us know if this challenge can be accepted and if #278 would be a viable solution. Regards, Teddy
Reopened since the solution is incomplete.
PR #285 addresses updating the provider to use https endpoints and how to configure for server trust.
@arjantijms Thank you for approving #285. Please let us know if 3.0.1-TCK could be staged for release. Thanks!
Hi @arjantijms, Please let us know if this challenge has been accepted or if more information is needed. Regards, Teddy
Hi @arjantijms, Please let us know if this challenge has been accepted or if more information is needed. Regards, Teddy
Greetings, This is a request for clarifications and perhaps get an update on this spec draft. Since the section https://github.com/jakartaee/security/blob/master/spec/src/main/asciidoc/openid.adoc#openidauthenticationmechanism refers to the HttpAuthenticationMechanism implementation, the following responses should be...
Greetings, I am reviewing the draft for implementation and the following section is problematic, > Step (3) in the OpenID Connect diagram depicted above, that is, when the OpenID Connect...
Hi, Yes. Also since notifying the container with something other than CredentialValidation.VALID results in AuthenticationStatus.FAILURE per https://github.com/jakartaee/security/blob/7572f4e002b0fbc308706593c67bfa9e61f12e5d/api/src/main/java/jakarta/security/enterprise/authentication/mechanism/http/HttpMessageContext.java#:~:text=AuthenticationStatus-,notifyContainerAboutLogin,-(CredentialValidationResult%20result)%3B, and the section is about authentication mechanism's return values, the wording is simplified...