SSL Keytool Mojo

Keytool setup: put the following into your .bash_profile:

JAVA_KEYSTORE="-keystore $JAVA_HOME/jre/lib/security/cacerts -storepass changeit"

DEMOTRUST_KEYSTORE="-keystore $WL_HOME/server/lib/DemoTrust.jks -storepass DemoTrustKeyStorePassPhrase"

This will make it easy to use keytool.  Then you can do:

keytool -list $JAVA_KEYSTORE

keytool -list $JAVA_KEYSTORE | grep rootca

keytool -delete -alias rootca $JAVA_KEYSTORE

keytool -import -alias rootca -file <filename> $JAVA_KEYSTORE

Tips on using SourceTree with Git.

One option is to not use a branch at all, just work on the master repo.
This is a good option for just uploading a bulk operation.
In this case, just change your files and Stage the changes.
Then just commit the changes and push them.

Create a develop branch.

Check out the develop branch.
Make your code changes.
Your new code should be in the File Status tab, Working Copy Changes.
Review your changes and click the up arrow to push all of your code to Staged Changes
Click Commit and enter an appropriate note.
Your develop branch will now be above your master branch.
Click on master and check it out.  Will see the purple as your main line.
Click Merge and select the develop branch.  (Commit merge immediately).
Develop and master should be on the same line.
Now do a push of master up to the remote branch.

OIM How-To set the xelsysadm password to never expire

To set the xelsysadm password to never expire, log into the database as the OIM schema owner and execute:

update usr set usr_pwd_warn_date=null, usr_pwd_expire_date=null,

usr_pwd_never_expires='1' where usr_login='XELSYSADM';

commit;

You can do this for any user.

How-To set the OIM database accounts to never expire

Because Oracle has put reasonable security limits into the default profile of the 11g database, when the OIM RCU runs it put the schema accounts into the default profile.  These account passwords will expire if you do not explicitly set them to not expire.  Assuming a Prefix of EDG the procedure will look like this:

$ sqlplus / as sysdba

SQL> CREATE PROFILE SERVICE_ACCOUNT

2    LIMIT PASSWORD_LIFE_TIME UNLIMITED

3    FAILED_LOGIN_ATTEMPTS UNLIMITED;

Profile created.

SQL> ALTER USER EDG_MDS PROFILE SERVICE_ACCOUNT;

User altered.

SQL> ALTER USER EDG_OIM PROFILE SERVICE_ACCOUNT;

User altered.

SQL> ALTER USER EDG_SOAINFRA PROFILE SERVICE_ACCOUNT;

User altered.

SQL> ALTER USER EDG_OPSS PROFILE SERVICE_ACCOUNT;

User altered.

SQL> ALTER USER EDG_ORASDPM PROFILE SERVICE_ACCOUNT;

User altered.

​

If the user passwords are due to or already have expired, go through all 5 of them (as sysdba) and re-set the password by entering (example for user EDG_OIM):

SQL> ALTER USER EDG_OIM IDENTIFIED BY <password>

Where <password> is the password of record, or a new password if you want to make those changes

Some updates 2015-June:

Use this script to get the list of profiles:

clear breaks
set linesize 120
set pagesize 10000

select * from dba_profiles;

Use this script to get the list of users:
clear breaks
set linesize 120
set pagesize 10000

select username, profile, account_status from dba_users;

For some systems you may have additional users to add to the profile.