OpenID Connect User Mapping
up vote
1
down vote
favorite
Currently my organization uses a number of web apps/mobile apps/APIs, some of which authenticate against an in-house IdP and others which use a third-party proprietary system (over which we have no control).
We have been asked to implement SSO for these web applications and as a result I have been reading up on OpenID Connect. I believe this would be a better solution than SAML given that (a) end-users are not always enterprise users, and (b) SAML not designed for mobile applications.
I believe I understand the flow reasonably well but have one sticking point. To allow users to authenticate using an external IdP, we would need to map the user back to our internal id. For example, user authenticates using OIDC/Google, resulting in us receiving the user's unique Google idenitifer (and email etc if we queried further), but this is not useful to us until we can map the Google identifier back to our internal customer id.
Is this mapping out of scope for OIDC? If so, is there a best-practice method for doing this? I'm sure we are not alone in this requirement...
Thanks,
John
single-sign-on openid-connect oidc
asked Nov 11 at 22:26
John
2492414
add a comment |
up vote
1
down vote
favorite
Currently my organization uses a number of web apps/mobile apps/APIs, some of which authenticate against an in-house IdP and others which use a third-party proprietary system (over which we have no control).
We have been asked to implement SSO for these web applications and as a result I have been reading up on OpenID Connect. I believe this would be a better solution than SAML given that (a) end-users are not always enterprise users, and (b) SAML not designed for mobile applications.
I believe I understand the flow reasonably well but have one sticking point. To allow users to authenticate using an external IdP, we would need to map the user back to our internal id. For example, user authenticates using OIDC/Google, resulting in us receiving the user's unique Google idenitifer (and email etc if we queried further), but this is not useful to us until we can map the Google identifier back to our internal customer id.
Is this mapping out of scope for OIDC? If so, is there a best-practice method for doing this? I'm sure we are not alone in this requirement...
Thanks,
John
single-sign-on openid-connect oidc
asked Nov 11 at 22:26
John
2492414
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
Currently my organization uses a number of web apps/mobile apps/APIs, some of which authenticate against an in-house IdP and others which use a third-party proprietary system (over which we have no control).
We have been asked to implement SSO for these web applications and as a result I have been reading up on OpenID Connect. I believe this would be a better solution than SAML given that (a) end-users are not always enterprise users, and (b) SAML not designed for mobile applications.
I believe I understand the flow reasonably well but have one sticking point. To allow users to authenticate using an external IdP, we would need to map the user back to our internal id. For example, user authenticates using OIDC/Google, resulting in us receiving the user's unique Google idenitifer (and email etc if we queried further), but this is not useful to us until we can map the Google identifier back to our internal customer id.
Is this mapping out of scope for OIDC? If so, is there a best-practice method for doing this? I'm sure we are not alone in this requirement...
Thanks,
John
single-sign-on openid-connect oidc
asked Nov 11 at 22:26
John
2492414
Currently my organization uses a number of web apps/mobile apps/APIs, some of which authenticate against an in-house IdP and others which use a third-party proprietary system (over which we have no control).
We have been asked to implement SSO for these web applications and as a result I have been reading up on OpenID Connect. I believe this would be a better solution than SAML given that (a) end-users are not always enterprise users, and (b) SAML not designed for mobile applications.
I believe I understand the flow reasonably well but have one sticking point. To allow users to authenticate using an external IdP, we would need to map the user back to our internal id. For example, user authenticates using OIDC/Google, resulting in us receiving the user's unique Google idenitifer (and email etc if we queried further), but this is not useful to us until we can map the Google identifier back to our internal customer id.
Is this mapping out of scope for OIDC? If so, is there a best-practice method for doing this? I'm sure we are not alone in this requirement...
Thanks,
John
single-sign-on openid-connect oidc
single-sign-on openid-connect oidc
asked Nov 11 at 22:26
John
2492414
asked Nov 11 at 22:26
John
2492414
asked Nov 11 at 22:26
John
2492414
asked Nov 11 at 22:26
John
2492414
asked Nov 11 at 22:26
John
2492414
2492414
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
Is this mapping out of scope for OIDC?
Short answer, yes.! If your backend require a comparison/validation with internal identity details, then it has to be done out-of-scope of OpenID Connect(OIDC) protocol. OIDC simply define the process of obtaining tokens (ID and access token), which are required for authentication and authorization.
is there a best-practice method for doing this?
One option is to use out of band directory synchronization. For example, Google provider Google Cloud Directory Sync (GCDS), which allows you to synchronize identity details to LDAP or MS Active directory. Other alternative is to use SCIM protocol to communicate and provision users dynamically. For example Google provide that support as well.
Alternatively, you can use just-in-time provision at the time you receive tokens. This support will depend on your identity provider implementation. For example, WSO2 identity server support both JIT provisioning as well as SCIM.
answered Nov 12 at 3:40
Kavindu Dodanduwa
5,52611230
1
Thanks for the response Kavindu. I presumed that I was asking too much of OpenID Connect to prescribe how to do this, but good to have it confirmed. I will investigate GCDS, JIT provisioning and SCIM.
– John
Nov 20 at 0:39
@John Every question have a value and not everyone has time to explore these protocols in depth. So glad to help you.
– Kavindu Dodanduwa
Nov 20 at 3:21
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
Is this mapping out of scope for OIDC?
Short answer, yes.! If your backend require a comparison/validation with internal identity details, then it has to be done out-of-scope of OpenID Connect(OIDC) protocol. OIDC simply define the process of obtaining tokens (ID and access token), which are required for authentication and authorization.
is there a best-practice method for doing this?
One option is to use out of band directory synchronization. For example, Google provider Google Cloud Directory Sync (GCDS), which allows you to synchronize identity details to LDAP or MS Active directory. Other alternative is to use SCIM protocol to communicate and provision users dynamically. For example Google provide that support as well.
Alternatively, you can use just-in-time provision at the time you receive tokens. This support will depend on your identity provider implementation. For example, WSO2 identity server support both JIT provisioning as well as SCIM.
answered Nov 12 at 3:40
Kavindu Dodanduwa
5,52611230
1
Thanks for the response Kavindu. I presumed that I was asking too much of OpenID Connect to prescribe how to do this, but good to have it confirmed. I will investigate GCDS, JIT provisioning and SCIM.
– John
Nov 20 at 0:39
@John Every question have a value and not everyone has time to explore these protocols in depth. So glad to help you.
– Kavindu Dodanduwa
Nov 20 at 3:21
add a comment |
up vote
0
down vote
accepted
Is this mapping out of scope for OIDC?
Short answer, yes.! If your backend require a comparison/validation with internal identity details, then it has to be done out-of-scope of OpenID Connect(OIDC) protocol. OIDC simply define the process of obtaining tokens (ID and access token), which are required for authentication and authorization.
is there a best-practice method for doing this?
One option is to use out of band directory synchronization. For example, Google provider Google Cloud Directory Sync (GCDS), which allows you to synchronize identity details to LDAP or MS Active directory. Other alternative is to use SCIM protocol to communicate and provision users dynamically. For example Google provide that support as well.
Alternatively, you can use just-in-time provision at the time you receive tokens. This support will depend on your identity provider implementation. For example, WSO2 identity server support both JIT provisioning as well as SCIM.
answered Nov 12 at 3:40
Kavindu Dodanduwa
5,52611230
1
Thanks for the response Kavindu. I presumed that I was asking too much of OpenID Connect to prescribe how to do this, but good to have it confirmed. I will investigate GCDS, JIT provisioning and SCIM.
– John
Nov 20 at 0:39
@John Every question have a value and not everyone has time to explore these protocols in depth. So glad to help you.
– Kavindu Dodanduwa
Nov 20 at 3:21
add a comment |
up vote
0
down vote
accepted
up vote
0
down vote
accepted
Is this mapping out of scope for OIDC?
Short answer, yes.! If your backend require a comparison/validation with internal identity details, then it has to be done out-of-scope of OpenID Connect(OIDC) protocol. OIDC simply define the process of obtaining tokens (ID and access token), which are required for authentication and authorization.
is there a best-practice method for doing this?
One option is to use out of band directory synchronization. For example, Google provider Google Cloud Directory Sync (GCDS), which allows you to synchronize identity details to LDAP or MS Active directory. Other alternative is to use SCIM protocol to communicate and provision users dynamically. For example Google provide that support as well.
Alternatively, you can use just-in-time provision at the time you receive tokens. This support will depend on your identity provider implementation. For example, WSO2 identity server support both JIT provisioning as well as SCIM.
answered Nov 12 at 3:40
Kavindu Dodanduwa
5,52611230
Is this mapping out of scope for OIDC?
Short answer, yes.! If your backend require a comparison/validation with internal identity details, then it has to be done out-of-scope of OpenID Connect(OIDC) protocol. OIDC simply define the process of obtaining tokens (ID and access token), which are required for authentication and authorization.
is there a best-practice method for doing this?
One option is to use out of band directory synchronization. For example, Google provider Google Cloud Directory Sync (GCDS), which allows you to synchronize identity details to LDAP or MS Active directory. Other alternative is to use SCIM protocol to communicate and provision users dynamically. For example Google provide that support as well.
Alternatively, you can use just-in-time provision at the time you receive tokens. This support will depend on your identity provider implementation. For example, WSO2 identity server support both JIT provisioning as well as SCIM.
answered Nov 12 at 3:40
Kavindu Dodanduwa
5,52611230
edited Nov 12 at 4:39
answered Nov 12 at 3:40
Kavindu Dodanduwa
5,52611230
answered Nov 12 at 3:40
Kavindu Dodanduwa
5,52611230
answered Nov 12 at 3:40
Kavindu Dodanduwa
5,52611230
5,52611230
1
Thanks for the response Kavindu. I presumed that I was asking too much of OpenID Connect to prescribe how to do this, but good to have it confirmed. I will investigate GCDS, JIT provisioning and SCIM.
– John
Nov 20 at 0:39
@John Every question have a value and not everyone has time to explore these protocols in depth. So glad to help you.
– Kavindu Dodanduwa
Nov 20 at 3:21
add a comment |
1
Thanks for the response Kavindu. I presumed that I was asking too much of OpenID Connect to prescribe how to do this, but good to have it confirmed. I will investigate GCDS, JIT provisioning and SCIM.
– John
Nov 20 at 0:39
@John Every question have a value and not everyone has time to explore these protocols in depth. So glad to help you.
– Kavindu Dodanduwa
Nov 20 at 3:21
1
1
Thanks for the response Kavindu. I presumed that I was asking too much of OpenID Connect to prescribe how to do this, but good to have it confirmed. I will investigate GCDS, JIT provisioning and SCIM.
– John
Nov 20 at 0:39
Thanks for the response Kavindu. I presumed that I was asking too much of OpenID Connect to prescribe how to do this, but good to have it confirmed. I will investigate GCDS, JIT provisioning and SCIM.
– John
Nov 20 at 0:39
@John Every question have a value and not everyone has time to explore these protocols in depth. So glad to help you.
– Kavindu Dodanduwa
Nov 20 at 3:21
@John Every question have a value and not everyone has time to explore these protocols in depth. So glad to help you.
– Kavindu Dodanduwa
Nov 20 at 3:21
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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%2f53253866%2fopenid-connect-user-mapping%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
