By: Kunal Vaidya user 27 Nov 2020 at 8:17 a.m. CST

2 Responses
Kunal Vaidya gravatar
Hey guys, We have a newly installed setup with 4.2.1 Gluu server with remote Couchbase and 2 OpenID clients configured. We use SCIM APIs for user onboarding and deletion. For some days, everything worked fine but now it throws this error: ``` 2020-11-26 00:36:17,706 ERROR [qtp790067787-19] [org.gluu.oxauth.service.SectorIdentifierService] (SectorIdentifierService.java:137) - Failed to get sub claim. PairwiseIdentifierService failed to find pair wise identifier. java.lang.NullPointerException: null 2020-11-26 00:36:17,708 ERROR [qtp790067787-19] [org.gluu.oxauth.model.crypto.OxAuthCryptoProvider] (OxAuthCryptoProvider.java:250) - Failed to find private key by kid: null, signatureAlgorithm: RS256(check whether web keys JSON in persistence corresponds to keystore file.) 2020-11-26 00:36:17,709 ERROR [qtp790067787-19] [org.gluu.oxauth.model.common.AuthorizationGrant] (AuthorizationGrant.java:187) - Failed to find private key by kid: null, signatureAlgorithm: RS256(check whether web keys JSON in persistence corresponds to keystore file.) java.lang.RuntimeException: Failed to find private key by kid: null, signatureAlgorithm: RS256(check whether web keys JSON in persistence corresponds to keystore file.) ```. For now we have disabled key regeneration as suggested in this support ticket https://support.gluu.org/single-sign-on/8428/openid-connect-error-private-key/. But we'll need a solution for this. Please can you look into the issue. Thanks!

By Yuriy Zabrovarnyy staff 02 Dec 2020 at 2:58 a.m. CST

Yuriy Zabrovarnyy gravatar
Please provide full logs with whole stacktrace. It's hard to guess by log snippets. My first guess is that your `pairwiseCalculationKey` configuration property is not set, however you set `pairwiseIdType` to `algorithmic`. Thus content of `oxAuthConfDynamic` attirbute (of `oxAuthConfiguration` OC) is welcome as well.

By Yuriy Zabrovarnyy staff 15 Dec 2020 at 3:46 a.m. CST

Yuriy Zabrovarnyy gravatar
Closing as this seems to be mis-configuration as described above. Feel free to re-open if needed.