Skip to content

Use idToken claims instead of UserInfo on Profile page#138

Open
bdemers wants to merge 1 commit intookta:masterfrom
bdemers:id-token-claims-on-profile
Open

Use idToken claims instead of UserInfo on Profile page#138
bdemers wants to merge 1 commit intookta:masterfrom
bdemers:id-token-claims-on-profile

Conversation

@bdemers
Copy link

@bdemers bdemers commented Aug 4, 2021

The "My User Profile (ID Token Claims)" does not actually contain all of the claims in the Id Token.

Looks like the previous logic used the user info instead?

}
},
async created () {
this.claims = await Object.entries(await this.$auth.getUser()).map(entry => ({ claim: entry[0], value: entry[1] }))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the map function here might be the cause

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That data returned from the user info endpoint isn't a 1-1 mapping of the token info. for example something like this:

const user = await this.$auth.getUser()
console.log("user: ", JSON.stringify(user))

Does not return all of the claims in the Id Token, it's missing all of the JWT related claims, the amr claim, auth_time, and any custom claims added via an Okta Token Inline Hook

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants