I have a Web Application that is implemented using Angular as a front-end and ASP.NET Web API 2 as back-end. The Application will be linked inside another application and the user will be redirected to the targeted application after he clicks on the link.
That's mean he will be redirected after he signed in using his credentials which is through the company Active Directory. Now my question, What is the mechanism that I should use to authorize the user based on his AD Information ? I am confused since my application
will not do the authentication and just focus on the authorization aspects ..
this will depend on how single sign on is implemented for your sites. You should be given an api to interface to the single sign on process. Typically this is shared domain cookie or oauth. You will need to find out.
None
0 Points
1 Post
Web API 2 Authorization
Dec 06, 2019 04:20 PM|fat.y|LINK
Good Day,
I need your support in the following scenario:
I have a Web Application that is implemented using Angular as a front-end and ASP.NET Web API 2 as back-end. The Application will be linked inside another application and the user will be redirected to the targeted application after he clicks on the link. That's mean he will be redirected after he signed in using his credentials which is through the company Active Directory. Now my question, What is the mechanism that I should use to authorize the user based on his AD Information ? I am confused since my application will not do the authentication and just focus on the authorization aspects ..
Thanks in advance
All-Star
54714 Points
13873 Posts
Re: Web API 2 Authorization
Dec 06, 2019 05:49 PM|bruce (sqlwork.com)|LINK
this will depend on how single sign on is implemented for your sites. You should be given an api to interface to the single sign on process. Typically this is shared domain cookie or oauth. You will need to find out.