Skip to main content
Post Closed as "Needs details or clarity" by svidgen, Bart van Ingen Schenau, CommunityBot
Bumped by Community user
Fixed grammar & spelling
Source Link
doubleYou
  • 2.9k
  • 1
  • 14
  • 26

I have multiple web services that need to be integrated into one solution. One frontend would provide access to features from all services. Each of the serviceservices has its own native authentication, and keep theirkeeps its own usersusers' data, services dont. Services don't support Oauth neither theOAuth or SAML. What I need to doachieve is that when a user gets logged in, he can actually access all services with one central account. ( howeverHowever, each service needs to have corresponding user data  ).

When a user is created it, he will have an account created in some central authentication service, as well as in all other services. So when the user authenticates against the central authorization service, it would be good if somehow the right credentials would be attached to requestrequests to a certain service.

Lets say I have A- authentication service B - some service C - some other service

  • A - authentication service
  • B - some service
  • C - some other service

whenWhen a user is created/registered on A automatically are created, accounts onon B and C are automatically created (with the same password can be used )and

when. When the user tries to access thea resource on B or C, if not authenticated, he will be redirected to authentication and after. After the authentication is succesfullsuccessful, the original request will have credentials attached for that service so that native authentication on the service B can be performed.

I have multiple web services that need to be integrated into one solution. One frontend would provide access to features from all services. Each of the service has its own native authentication and keep their own users data, services dont support Oauth neither the SAML. What I need to do is that when user gets logged in he can actually access all services with one central account ( however each service needs to have corresponding user data  ).

When user is created it will have account created in some central authentication service as well as in all other services. So when user authenticates against the central authorization service it would be good if somehow right credentials would be attached to request to certain service.

Lets say I have A- authentication service B - some service C - some other service

when user is created/registered on A automatically are created accounts on B and C ( same password can be used )and

when user tries to access the resource on B or C if not authenticated he will be redirected to authentication and after the authentication is succesfull original request will have credentials attached for that service so that native authentication on the service B can be performed.

I have multiple web services that need to be integrated into one solution. One frontend would provide access to features from all services. Each of the services has its own native authentication, and keeps its own users' data. Services don't support OAuth or SAML. What I need to achieve is that when a user gets logged in, he can actually access all services with one central account. (However, each service needs to have corresponding user data).

When a user is created, he will have an account created in some central authentication service, as well as in all other services. So when the user authenticates against the central authorization service, it would be good if somehow the right credentials would be attached to requests to a certain service.

Lets say I have

  • A - authentication service
  • B - some service
  • C - some other service

When a user is created/registered on A, accounts on B and C are automatically created (with the same password). When the user tries to access a resource on B or C, if not authenticated, he will be redirected to authentication. After the authentication is successful, the original request will have credentials attached for that service so that native authentication on the service B can be performed.

Source Link
mirkash
  • 119
  • 2

User registration across multiple services

I have multiple web services that need to be integrated into one solution. One frontend would provide access to features from all services. Each of the service has its own native authentication and keep their own users data, services dont support Oauth neither the SAML. What I need to do is that when user gets logged in he can actually access all services with one central account ( however each service needs to have corresponding user data ).

When user is created it will have account created in some central authentication service as well as in all other services. So when user authenticates against the central authorization service it would be good if somehow right credentials would be attached to request to certain service.

Lets say I have A- authentication service B - some service C - some other service

when user is created/registered on A automatically are created accounts on B and C ( same password can be used )and

when user tries to access the resource on B or C if not authenticated he will be redirected to authentication and after the authentication is succesfull original request will have credentials attached for that service so that native authentication on the service B can be performed.