2

I am working to move an ASP.NET MVC site currently using FormsAuthentication to use SSO (Webgate/OAM).

The Webgate is installed and exposed thru an ISAPI filter on IIS and redirects to SSO page.

In FormsAuthentication, we would get HttpContext.Current.User as IPrincipal. But with SSO authentication, IPrincipal in HttpContext.Current.User is no over available.

This documentation from Oracle says that protected ASP.Net should expect WindowsPrincipal as its IPrincipal. But replacing HttpContext.Current.User with WindowsPrincipal is not helping either.

Is there a way I can capture the identity of authenticated user inside ASP.NET application?

Arpit Khandelwal
  • 1,743
  • 3
  • 23
  • 34
  • A question from a new user (can't comment) - "Can you please share the code you used to get the response sent by oam please?" – bwegs Mar 11 '15 at 15:20

2 Answers2

1

Time revealed that when SSO redirected authenticated user, back to my app, it shared username in HTTP headers. I realize I should have dig thru the SSO response.

Anyways, I was able to capture the identity of the user and set up FormsAuthentication cookie with this identity. This approach left me here, if anyone has an interest to follow it.

Community
  • 1
  • 1
Arpit Khandelwal
  • 1,743
  • 3
  • 23
  • 34
0

OAM 11g Now supports OOTB integration with the .Net Applications (MVC). You can refer the http://howtoidm.blogspot.in/2015/03/oam-11g-net-application-integration.html

anil
  • 961
  • 1
  • 11
  • 23