Hi Team, Upgraded to v0.10.2 on GKE and using ping...
# troubleshoot
q
Hi Team, Upgraded to v0.10.2 on GKE and using pingfed for the integration with below configuration: name: AUTH_OIDC_CLIENT_ID value: client_id - name: AUTH_OIDC_CLIENT_SECRET value: secret - name: AUTH_OIDC_DISCOVERY_URI value: https://dns/.well-known/openid-configuration - name: AUTH_OIDC_BASE_URL value: https://dns - name: AUTH_OIDC_SCOPE value: openid profile email - name: AUTH_OIDC_USER_NAME_CLAIM value: email - name: METADATA_SERVICE_AUTH_ENABLED value: "true" - name: AUTH_OIDC_JIT_PROVISIONING_ENABLED value: "true" - name: AUTH_OIDC_PRE_PROVISIONING_REQUIRED value: "false" - name: AUTH_JAAS_ENABLED value: "false" getting SSO error : "java.util.concurrent.CompletionException: org.pac4j.core.exception.TechnicalException: Unsigned ID tokens are not allowed: they must be explicitly enabled on client side and the response_type used must return no ID Token from the authorization endpoint at" cc: @bland-artist-80619
🔍 1
✅ 1
📖 1
l
This content can't be displayed.
q
Resolved the issue.
h
@quaint-barista-82836 - how did you resolve this issue ? I am facing something similar
q
@handsome-football-66174 try to use the algorithm that you use to unsign the token_id
name: AUTH_OIDC_PREFERRED_JWS_ALGORITHM value: RS256
h
@quaint-barista-82836 - How do we find out the alogrithm used, is it at the SSO provider side ?
q
@handsome-football-66174 you can get the JWT to token and check the algorithm used, if you are not able to figure out work with sso team and check the configuration they have used
h
@quaint-barista-82836 - Thank you for the suggestion ! Worked like a charm
Copy code
- name: AUTH_OIDC_PREFERRED_JWS_ALGORITHM
  value: RS256