Showing posts with label Identity Management. Show all posts
Showing posts with label Identity Management. Show all posts

Thursday, October 1, 2015

Reset the AdminServer password in WebLogic Server


Step 1: Setup environment variables.
[omss@ptud security]$ export MW_HOME=/home/omss/middleware
[omss@ptud security]$ export DOMAIN_HOME=/home/omss/middleware/user_projects/domains/oud_domain

Step 2: Shutdown the WebLogic domain
$DOMAIN_HOME/bin/stopWebLogic.sh

Step 3: Rename the data folder.
[omss@ptud security]$ mv $DOMAIN_HOME/servers/AdminServer/data/ $DOMAIN_HOME/servers/AdminServer/data-old

Step 4: Set environment
[omss@ptud security]$ .  $DOMAIN_HOME/bin/setDomainEnv.sh

Step 5: Reset the password
[omss@ptud oud_domain]$ cd $DOMAIN_HOME/security
 [omss@ptud security]$ java weblogic.security.utils.AdminAccount weblogic 12345678 .

Step 6: Update file boot.properties
[omss@ptud security]$ cd $DOMAIN_HOME/servers/AdminServer/security/
[omss@ptud security]$ vi boot.properties
#Thu Oct 01 10:56:21 ICT 2015
username=weblogic
password=12345678

Step 7: Start the WebLogic domain
$DOMAIN_HOME/bin/startWebLogic.sh


Friday, September 25, 2015

Integrate BI Publisher with Single Sign-On

Architecture:


It’s the same way to do. Read this article for details


Here, I determine the difference between them.

Configure OHS


[obiee@ptudvtg142 ohs1]$ pwd
/home/obiee/middleware/Oracle_WT1/instances/instance1/config/OHS/ohs1
[obiee@ptudvtg142 ohs1]$ more mod_wl_ohs.conf

# NOTE : This is a template to configure mod_weblogic.

LoadModule weblogic_module   "${ORACLE_HOME}/ohs/modules/mod_wl_ohs.so"

# This empty block is needed to save mod_wl related configuration from EM to this file when changes are made at the Base Virtual Host Level
<fModule weblogic_module>
#      WebLogicHost
#      WebLogicPort
#      Debug ON
#      WLLogFile /tmp/weblogic.log
#      MatchExpression *.jsp
</IfModule>

# <Location /weblogic>
#      SetHandler weblogic-handler
#      PathTrim /weblogic
#      ErrorPage  http:/WEBLOGIC_HOME:WEBLOGIC_PORT/
#  </Location>
<Location /xmlpserver>
      SetHandler weblogic-handler
      WebLogicHost 192.168.2.142
      WebLogicPort 9704
</Location>

<Location /analytics>
      SetHandler weblogic-handler
      WebLogicHost 192.168.2.142
      WebLogicPort 9704
</Location>

[obiee@ptudvtg142 ohs1]$

Configure BI Publisher for SSO

Step 1: Login BI Publisher as administrator
Choose Administration à Security Center à Security Configuration 
















Step 2: On Authentication area, Tick Use Single Sign-On
Single Sign-on Type: Oracle Access Manager
How to get username: HTTP Header
User Name Parameter: OAM_REMOTE_USER
How to get user locale: HTTP Parameter
User Locale Parameter LOCALE_LANGUAGE
Click Apply.















Step 3: Reboot Weblogic Server (AdminServer) and Managed Server (bi_server1)

Test Single Sign-On:

Step 1: Login to BI Publisher via OHS







Step 2: Redirect to OAM login Form













Step 3: Enter username and password and click Login






















Step 4: Login Successful

Wednesday, September 23, 2015

Integrate Content Repository (WCCC) with Single Sign-On



Architecture:



Roadmap to Configuring OAM










Step by Step:

1: Install and configure OAM and OUD.

a. Install and Configure OAM
b. Install and Configure OUD

Detail read it:

c. Integrate OAM with OUD:

Read it:

2: Configure the WebLogic domain for OAM

2a: Configure the OUD authenticator

Step 1: Login to Weblogic Server Console.

Step 2:Click Security Realms



































Step 3:Click myrealm

Step 4: On Providers tab, Click New

Step 5: enter value for fields following:
Name: OUD Authenticator
Type: IPlanetAuthenticator
Then Click OK

Step 6:Click OUD Authenticator


Step 7: enter value for fields following:
Host: 192.168.2.156
Port: 1389 is default
Principal: Default: cn= Directory Manager
Credential: < Password Root user DN>
Confirm Credential:
User Base DN:< user of Directory Base DN> On my office, ou=people,dc=ptud,dc=com
Group Base DN: On my my office, ou=groups,dc=ptud,dc=com
Tick Use Retrieved User Name as Principal as selected.
Click Save.


You also check on OUD server.

2b: Configure the OAM Identity Asserter

Step 1: Login Weblogic Console on server 192.168.2.156

Step 2: Security Realms à myrealm à Providers. Click New.

Step 3: enter value for fields following:
Name: OAM ID Asserter
Type: OAMIdentityAsserter
Click OK.


Step 4: click OAM ID Asserter
Control Flag: Required
Active Type: Chosen( OAM_REMOTE_USER,OAM_IDENTITY ASSERTER, ObSSOCookie )
Click OK.


2c: Configure the default authenticator and provider order

Step 1: Homeà Security Realms à myrealmàProviders. Click Reorder
Step 2: Order Authentication Providers following:
1.      OAM ID Asserter
2.      OUD Authenticator
3.      Others
Click OK

2d:Add an OAM SSO provider

3: Install and configure OHS

Install and configure OHS on server 192.168.2.156

[wccc@ptud ohs1]$ pwd
/home/wccc/fmw/Oracle_WT1/instances/instance1/config/OHS/ohs1
[wccc@ptud ohs1]$ ls
admin-bin   auditconfig.xml  cgi-bin               component-logs.xml  error    fcgi-bin  httpd.conf       icons      magic  manual      mod_plsql   mod_wl_ohs.conf      proxy-wallet  webgate
admin.conf  backup           component_events.xml  disabled            fastcgi  htdocs    httpd.conf.ORIG  keystores  man    mime.types  moduleconf  mod_wl_ohs.conf.bak  ssl.conf      webgate.conf
[wccc@ptud ohs1]$ vi mod_wl_ohs.conf
# NOTE : This is a template to configure mod_weblogic.

LoadModule weblogic_module   "${ORACLE_HOME}/ohs/modules/mod_wl_ohs.so"

# This empty block is needed to save mod_wl related configuration from EM to this file when changes are made at the Base Virtual Host Level
<IfModule weblogic_module>
#      WebLogicHost < WEBLOGIC_HOST>
#      WebLogicPort < WEBLOGIC_PORT>
#      Debug ON
#      WLLogFile /tmp/weblogic.log
#      MatchExpression *.jsp
</IfModule>

# < Location /weblogic>
#      SetHandler weblogic-handler
#      PathTrim /weblogic
#      ErrorPage  http:/WEBLOGIC_HOME:WEBLOGIC_PORT/
#  < /Location>


<Location /cs>
      SetHandler weblogic-handler
      WebLogicHost 192.168.2.142
      WebLogicPort 16200
</Location>

[wccc@ptud ohs1]$

4: Additional Configurations

5: Install and configure WebGate:

Deploying WebGate to OHS see more
Registering WebGate to OAM see more

6: Testing SSO

Step 1: Access http://192.168.2.142:7777/cs via web browser


Step 2: Redirect OAM login

Step 3: enter username and password and click login.


Step 4: Login successful.


Tuesday, September 22, 2015

Registering Oracle HTTP Server WebGate with Oracle Access manager



Step 1: Setup the RREG utility 
[omss@ptudvtg149 ~]$ cd fmw/
[omss@ptudvtg149 fmw]$ ls
coherence_3.7  domain-registry.xml  logs  modules  ocm.rsp  oracle_bip  oracle_common  Oracle_IDM1  registry.dat  registry.xml  user_projects  utils  wlserver_10.3
[omss@ptudvtg149 fmw]$ mkdir oam-rreg
[omss@ptudvtg149 fmw]$ cd oam-rreg/
[omss@ptudvtg149 oam-rreg]$ cp /home/omss/fmw/Oracle_IDM1/oam/server/rreg/client/RREG.tar .
[omss@ptudvtg149 oam-rreg]$ ls
RREG.tar
[omss@ptudvtg149 oam-rreg]$ tar -xvf RREG.tar
rreg/
rreg/logs/
rreg/bin/
rreg/bin/oamreg.bat
rreg/bin/oamreg.sh
rreg/input/
rreg/input/OAMRequest.xml
rreg/input/OAMRequest_short.xml
rreg/input/OAM11GRequest.xml
rreg/input/OpenSSOUpdateAgentRequest.xml
rreg/input/CreatePolicyRequest.xml
rreg/input/OAM11GRequest_short.xml
rreg/input/OSSORequest.xml
rreg/input/OpenSSORequest_short.xml
rreg/input/OSSOUpdateAgentRequest.xml
rreg/input/OAM11GUpdateAgentRequest.xml
rreg/input/OpenSSORequest.xml
rreg/input/UpdatePolicyRequest.xml
rreg/input/OAMUpdateAgentRequest.xml
rreg/lib/
rreg/lib/utilities.jar
rreg/lib/RequestResponse.jar
rreg/lib/rreg.jar
rreg/lib/commons-logging-1.1.1.jar
rreg/lib/osdt_cert.jar
rreg/lib/identitystore.jar
rreg/lib/oraclepki.jar
rreg/lib/commons-codec-1.3.jar
rreg/lib/commons-httpclient-3.1.jar
rreg/lib/jps-common.jar
rreg/lib/nap-api.jar
rreg/lib/osdt_core.jar
rreg/lib/ojmisc.jar
rreg/lib/osdt_xmlsec.jar
rreg/lib/jps-internal.jar
rreg/lib/jps-ee.jar
rreg/lib/jps-unsupported-api.jar
rreg/lib/jps-api.jar
rreg/config/
rreg/config/RequestResponseXMLSchema.xsd
rreg/templates/
rreg/templates/opensso/
rreg/templates/opensso/webagents/
rreg/templates/opensso/webagents/OpenSSOAgentConfiguration.template
rreg/templates/opensso/webagents/OpenSSOAgentBootstrap.template
rreg/templates/opensso/webagents/AMAgent.template
rreg/templates/opensso/j2eeagents/
rreg/templates/opensso/j2eeagents/OpenSSOAgentConfiguration.template
rreg/templates/opensso/j2eeagents/AMAgent.template
rreg/templates/opensso/j2eeagents/OpenSSOAgentBootstrap.template
rreg/tester/
rreg/tester/nap-api.jar
rreg/tester/oamtest.jar
rreg/truststore/
rreg/truststore/rregcerts.jks
rreg/output/
[omss@ptudvtg149 oam-rreg]$ ls
rreg  RREG.tar

Step 2: Use the existing Request template file to create the configuration file 

Monday, September 21, 2015

Deploying the Oracle HTTP Server WebGate Instance

1.      Go to the WebGate_Home/webgate/ohs/tools/deployWebGate directory by running the following command:
cd WebGate_Home/webgate/ohs/tools/deployWebGate
[access@ptud ~]$ cd fmw/Oracle_WebGate/webgate/ohs/tools/deployWebGate/

2.      Run the following command to copy the required bits of agent from the WebGate_Home directory to the WebGate_Instance location:
./deployWebGateInstance.sh -w WebGate_Instance_Directory -oh WebGate_Oracle_Home
In this command:
o    WebGate_Oracle_Home is the directory in which you have installed Oracle HTTP Server WebGate and created it as the Oracle home for WebGate.
Example:
MW_HOME/Oracle_OAMWebGate1
o    WebGate_Instance_Directory is the location of WebGate Instance Home, which is same as the Instance Home of Oracle HTTP Server.
Example:
MW_HOME/Oracle_WT1/instances/instance1/config/OHS/ohs1
Note:
An Instance Home for Oracle HTTP Server is created after you configure Oracle HTTP Server. This configuration is performed after installing Oracle HTTP Server 11.1.1.2.0 or patching to Oracle HTTP Server 11.1.1.5.0.
[access@ptud deployWebGate]$ ./deployWebGateInstance.sh -w /home/access/fmw/Oracle_WT1/instances/instance1/config/OHS/ohs1 -oh /home/access/fmw/Oracle_WebGate/
Copying files from WebGate Oracle Home to WebGate Instancedir

3.      Run the following command to ensure that the LD_LIBRARY_PATH variable contains Oracle_Home_for_Oracle_HTTP_Server/lib:
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:Oracle_Home_for_Oracle_HTTP_Server/lib
[access@ptud deployWebGate]$ export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/access/fmw/Oracle_WT1/lib

4.      From your present working directory, move up one directory level:
WebGate_Home/webgate/ohs/tools/setup/InstallTools
[access@ptud deployWebGate]$ cd /home/access/fmw/Oracle_WebGate/webgate/ohs/tools/setup/InstallTools/
[access@ptud InstallTools]$ ls
apache_webgate.template  EditHttpConf

5.      On the command line, run the following command to copy the apache_WebGate.template from the WebGate_Home directory to the WebGate Instance location (re-named toWebGate.conf) and update the httpd.conf file to add one line to include the name of WebGate.conf:
./EditHttpConf -w WebGate_Instance_Directory [-oh WebGate_Oracle_Home] [-o output_file]
Note:
The -oh WebGate_Oracle_Home and -o output_file parameters are optional.
In this command:
o    WebGate_Oracle_Home is the directory where you have installed Oracle HTTP Server WebGate for Oracle Access Manager and created as the Oracle Home for WebGate.
Example:
MW_HOME/Oracle_OAMWebGate1
o    WebGate_Instance_Directory is the location of WebGate Instance Home, which is same as the Instance Home of Oracle HTTP Server.
Example:
MW_HOME/Oracle_WT1/instances/instance1/config/OHS/ohs1
o    output_file is the name of the temporary output file used by the tool.
Example:
Edithttpconf.log
[access@ptud InstallTools]$ ./EditHttpConf -w /home/access/fmw/Oracle_WT1/instances/instance1/config/OHS/ohs1 -oh /home/access/fmw/Oracle_WebGate/
The web server configuration file was successfully updated
/home/access/fmw/Oracle_WT1/instances/instance1/config/OHS/ohs1/httpd.conf has been backed up as /home/access/fmw/Oracle_WT1/instances/instance1/config/OHS/ohs1/httpd.conf.ORIG



Wednesday, September 16, 2015