Staff

@raphaelmcgee Ah, sorry, I missed that you were already using the OIDC provider. Let me take a look at get back to you.

@raphaelmcgee

If this is blocking you, one option would be to try the OpenID Connect Identity Provider, documented here: https://fusionauth.io/docs/v1/tech/identity-providers/openid-connect/

From scanning the LinkedIn docs, it looks like they support OpenID Connect.

Will report back with more info as I investigate.

@raphaelmcgee Ah, thanks, the MS docs are what I was looking for.

@ccantrell hmmm. We'll take a look at this.

You should be able to clone the repository and run the complete application following the instructions here: https://github.com/FusionAuth/fusionauth-quickstart-dotnet-web

Can you please give that a try and see if you run into the same issue?

@raphaelmcgee Can you please share the link to the LinkedIn docs you followed?

Also, what does the event log say?

@lambert-torres Hmmm.

Since you have a paid plan, I've escalated this to engineering support.

I'll follow up here with a resolution for future readers.

@lambert-torres

Ah, you'll need to modify the email template, then.

Here's an example template: https://fusionauth.io/docs/v1/tech/email-templates/templates-replacement-variables#email-verification

Make sure you update both the HTML and TXT versions of the template.

Let me know if that works.

@lambert-torres Any place you want to use premium features, you need to enter a license. However, for your staging environment, you can use the non-production version, which won't count MAU (and therefore won't count toward your cost).

Here's more info: https://fusionauth.io/docs/v1/tech/admin-guide/licensing

Hi @prawee ,

You can't add any more fields to the login record. If you'd like to add a GitHub issue with your use case and details, that'd be helpful: https://github.com/FusionAuth/fusionauth-issues/issues/

Thanks,
Dan

Hi @lou,

I was unable to replicate this issue. I'm using 1.47.1.

I used the login API for simplicity. I set up an application to Generate Refresh Tokens and Enable JWT refresh on the Security tag.

I set up that application up with three roles, and a group with one of those roles. I then assigned a user to that group.

I called the Login API and got back a refresh token as well as an access token. I examined the access token and saw the expected one role.

I then added another role to group. Then I called the /api/jwt/refresh endpoint and looked at the resulting access token. That access token had 2 roles now.

Here are the two requests:

curl -H 'Authorization: bf69486b-4733-4470-a592-f1bfce7af580' http://localhost:9011/api/login -d '{"applicationId":"85a03867-dccf-4882-adde-1a79aeec50df","loginId":"admin@example.com","password":"password"}' -H 'Content-type: application/json'

curl -H 'Authorization: bf69486b-4733-4470-a592-f1bfce7af580' http://localhost:9011/api/jwt/refresh -d '{"refreshToken": "fYFIudBHGFJMsBrmufiTJjvczKYkq6BvNTn3B6oIKRvXn4mJd4NQdA"}' -H 'Content-type: application/json'

A few more questions to see if we can track down this behavior:

• What version of FusionAuth are you running?
• Can you provide more detailed recreate steps?
• Did you use the authorization code grant?
• Did you do something else between the initial login and the token refresh?
• How did you update the group role setting?
• How many nodes of FusionAuth are you running?

Thanks,
Dan