OAM 11g .NET Integration - Part 2

Why is it different from OAM 11g .NET Integration?

.NET App developers need not to worry about handling the Roles and Identity in their code. The authentication, authorization, Session Management, SSO responsibility will be handled by the OAM infra. This mode of deployment will decouple App development and Access Management responsibilities. Isn't it cool.

How to integrate?

Prerequisite:

1. OAM R2PS2 +, IIS 11g R2PS2 WebGate, OAM IISImpersonationModule.dll and ObPrincipalHttpModule.dll (Opional).
2. IIS 7.X or higher.
3. A .Net Application
4. Active Directory.

Integration Steps:

1. Deploy the .Net application on the IIS Site.
2. Install and configure OAM Server and OAM WebGate for IIS.
3. Configure IISImpersonationModule.dll Native module for the Site hosting the .Net Application.
4. Add SharePoint UserName and Password in OAM WebGate profile in the OAM admin console.
5. Add a authz policy for success, set the HTTP Header "IMPERSONATE" with $user.userid.
6. [Optional]If you are going to use Roles instead of Identity then use ObPrincipalHttpModule.dll and set the configuration(web.config) as mentioned in the previous post.
7. Make sure that the IIS Site -> Authentication -> Provider has ASP .Net Impersonation enabled.
8. 
   

I

OAP/NAP Analysis using Wireshark - Part 2

How to identify the ciphersuite used in OAP/NAP for Simple & Cert Mode Communication?

1. Capture OAP/NAP Messages as mentioned in previous blog.
2. Open the tcpdump captured file (/tmp/wg.cap) using Wireshark.
3. Once the tcpdump file is opened in the Wireshark, click Analyze->Decode As, then select SSL.
4. Find the Client Hello Packet in Wireshark, as shown in the screenshot.  The Client Hello is part of SSL Handshake.

   

   Client Hello.

5. Find the Server Hello packet in Wireshark, as shown in screenshot. This Server Hello is part of SSL handshake.

   

   Server Hello.