Identity Server 4 - Updating Claims Provided By An External Provider
up vote
1
down vote
favorite
Not sure if i'm missing something here or if its something that needs to be done in a custom way (Or even if what I'm trying is bad practice). Consider the following Scenario.
- A User chooses to log in via a external provider to my IDS4 server.
- IDS4 automatically provisions a local user and completes the sign-in of the user. My application is interested in a 'phone_number' claim and so copies this value to its local store.
- Later on the User updates their 'phone_number' in the external provider. So now the claim in my local IDS4 store is out of date.
What is the best way to update my local 'phone_number' claim. If i'm using a sliding refresh token there's a chance that it could be a very long time before a user has to re-authenticate against the original exteranl provider and realise this claim has been updated.
In this particular case I have access to both the IDS4 instance and the External provider.
identityserver4 oidc
add a comment |
up vote
1
down vote
favorite
Not sure if i'm missing something here or if its something that needs to be done in a custom way (Or even if what I'm trying is bad practice). Consider the following Scenario.
- A User chooses to log in via a external provider to my IDS4 server.
- IDS4 automatically provisions a local user and completes the sign-in of the user. My application is interested in a 'phone_number' claim and so copies this value to its local store.
- Later on the User updates their 'phone_number' in the external provider. So now the claim in my local IDS4 store is out of date.
What is the best way to update my local 'phone_number' claim. If i'm using a sliding refresh token there's a chance that it could be a very long time before a user has to re-authenticate against the original exteranl provider and realise this claim has been updated.
In this particular case I have access to both the IDS4 instance and the External provider.
identityserver4 oidc
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
Not sure if i'm missing something here or if its something that needs to be done in a custom way (Or even if what I'm trying is bad practice). Consider the following Scenario.
- A User chooses to log in via a external provider to my IDS4 server.
- IDS4 automatically provisions a local user and completes the sign-in of the user. My application is interested in a 'phone_number' claim and so copies this value to its local store.
- Later on the User updates their 'phone_number' in the external provider. So now the claim in my local IDS4 store is out of date.
What is the best way to update my local 'phone_number' claim. If i'm using a sliding refresh token there's a chance that it could be a very long time before a user has to re-authenticate against the original exteranl provider and realise this claim has been updated.
In this particular case I have access to both the IDS4 instance and the External provider.
identityserver4 oidc
Not sure if i'm missing something here or if its something that needs to be done in a custom way (Or even if what I'm trying is bad practice). Consider the following Scenario.
- A User chooses to log in via a external provider to my IDS4 server.
- IDS4 automatically provisions a local user and completes the sign-in of the user. My application is interested in a 'phone_number' claim and so copies this value to its local store.
- Later on the User updates their 'phone_number' in the external provider. So now the claim in my local IDS4 store is out of date.
What is the best way to update my local 'phone_number' claim. If i'm using a sliding refresh token there's a chance that it could be a very long time before a user has to re-authenticate against the original exteranl provider and realise this claim has been updated.
In this particular case I have access to both the IDS4 instance and the External provider.
identityserver4 oidc
identityserver4 oidc
asked Nov 9 at 15:12
Lee
215
215
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53228380%2fidentity-server-4-updating-claims-provided-by-an-external-provider%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown