brvaland
commented
5 years ago Further update on my issue, i have managed to get public signing key from okta - https://developer.okta.com/docs/api/resources/oidc/#keys
I have converted JWK to PEM using this tool - https://8gwifi.org/jwkconvertfunctions.jsp
Replaced TALK_JWT_SECRET with TALK_JWT_SECRETS as below
TALK_JWT_SECRETS=[{"kid":"-0UTDvXAKmQo2C6a97BCr-DJ7JEfwpFdbgFy3PAvvqY","public":"-----BEGIN PUBLIC KEY-----\\n*******************\\n-----END PUBLIC KEY-----\\n"}]I have verified token (jwt.io) as below.
{
"kid": "-0UTDvXAKmQo2C6a97BCr-DJ7JEfwpFdbgFy3PAvvqY",
"alg": "RS256"
}
{
"ver": 1,
"jti": "AT.mExZ7QrNCgJbSLGaZnAKLxWNhHn4Qsq7nY9d9kHFRDQ",
"iss": "https://dev-***.oktapreview.com/oauth2/default",
"aud": "api://default",
"iat": 1556192231,
"exp": 1556195831,
"cid": "0oakhu3pfpTyVhl160h7",
"uid": "00ufwg9tbbeCc4bnh0h7",
"scp": [
"openid"
],
"sub": "******"
}```
wyattjoh
maveonair
Hi
I would like to integration coral talk with Okta for SSO and it is not working. I am newbie to talk and plugins. I am not sure what i need to specify for TALK_JWT_SECRET as OKTA using JSON Web Key Set - https://developer.okta.com/code/dotnet/jwt-validation/
I have done the following setups
module.exports = {
// When the JWT is passed to Talk, first it will be validated // Next, Talk will attempt to locate a user in its DB using the token's sub claim, // if the user is not found, the tokenUserNotFound hook will be called to create the user tokenUserNotFound: async ({ jwt }) => { debug('The jwt is ' + JSON.stringify(jwt));
},
// At this point we've handled creating new users, // now let's handle updating a user that was created by our tokenUserNotFound hook. // This implementation assumes that the external auth service calls the TALK_ROOT_URL/plugin/update-user endpoint // with a valid jwt token anytime a user is update needs to be passed to Talk // First we add the `/plugin/update-user`` route and secure it with ADMIN level permissions router: router => { router.post( '/plugin/update-user', authz.needed('ADMIN'), async (req, res, next) => { const { body: { token }, context: { connectors: { models: { User }, }, }, } = req;
},
// This last step is completely OPTIONAL, // and only applies if you need to override a standard Talk data point with your own custom value. // This example assumes that I've stored a custom displayName value in the User.metadata property // Here we will reference the value in User.metadata.displayName everywhere that User.username is shown in Talk resolvers: { User: { username: user => get(user, 'metadata.displayName', get(user, 'username')), }, }, };