OAM 11g .Net Application Integration

 OAM 11g supports OOTB integration with .Net Application including MVC, Sliverlight applications. The OAM Principal and roles can be consumed by the .Net Application using OAM .Net connector aka ObPrincipalHttpModule.

Prerequisite:

1.  OAM R2PS2 and IIS 11g R2PS2 WebGate.
2.  IIS 7.X or Higher.
3. A .NET Application implementing "Context.User.IsInRole("SomeOAMRole")" API.
4.  .NET 4.0

OAM .Net Application Integration Steps

1.      Create a .net application and deploy it on IIS WebServer.

2.      Create OAM Authz Policy to set OAMHttpModule Role=<SomeRole>&Role=<someRole>.

3.      Add ObPrincipalHttpModule.dll to Global Assembly Cache (GAC) on IIS box. The command is

gacutil -i ObPrincipalHttpModule.dll

Command to verify if ObPrincipalHttpModule is added to GAC.

gacutil -l | grep ObPrincipalHttpModule

           4.       Update the web.config of IIS Site hosting .Net Application. (Note: web.config of the .net application can also be modified to add ObPrincipalHttpModule). Following should be updated in web.config <configuration> tag.

For Integrated( IIS Application ) Mode:

<system.webServer>
<customErrors mode="Off" /> -->
<modules>
<add name="OAMHttpModule" type="Oracle.OAM.Agents.OAMHttpModule,ObPrincipalHttpModule, Version=12.0.0.0, Culture=neutral,PublicKeyToken=99645062befa5197" />
</modules>
</system.webServer>

For Classic (IIS Application ) Mode:

<system.web>

<httpModules>
<add type="Oracle.OAM.Agents.OAMHttpModule,ObPrincipalHttpModule, Version=12.0.0.0, Culture=neutral,PublicKeyToken=99645062befa5197" name="OAMHttpModule" />
</httpModules>

</system.web>