Home » forums » SCT Banner Integration

Lost SSO with Banner 8

Submitted by aayers on Tue, 2010-03-23 13:41

We completed an upgrade to Banner 8 last week and lost SSO to INB and SSO.   I'm getting the 'Unsupported OID Service' error and I suspect that it can be fixed by re-entering the bind password on GUAUPRF.   I have been unable to do that due to a forms error -  40509.  So, I 've tried to do the same using the reencrypt.sql script in the install directory.  This gives me the following: 

DECLARE
*
ERROR at line 1:
ORA-29283: invalid file operation
ORA-06512: at "SYS.UTL_FILE", line 536
ORA-29283: invalid file operation
ORA-06512: at "BANSSO.GOKKSSO", line 18
ORA-06512: at "GENERAL.GT_GURUPRF_PRE_UPDATE_ROW", line 19
ORA-04088: error during execution of trigger
'GENERAL.GT_GURUPRF_PRE_UPDATE_ROW'
ORA-06512: at line 7

So, I'm pretty much dead in the water for SSO.   Is this in any way related to special characters in the bind password?   Any ideas on how to resolve the issue? 

 Al

‹ id number in Blackboard Gradebook customizing error messages in luminis for banner delivered channels ›

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Same thing here...

Submitted by benhall on Thu, 2010-03-25 12:11.

I completed the Banner 8 upgrade in February and also had a complete SSO meltdown.

By any chance did any of the following change during the course of the upgrade?

- Your oracle SID

- Your OAS DAD name for SSB?

Those were two of the things that caused us problems and had to be resolved to get things working again.

 

Have you verified that LMB is working properly since the upgrade?  That could be an issue that you don't immediately notice.

Password

Submitted by Christine on Thu, 2010-03-25 13:25.

When we upgraded to Banner 8, we also had to change the bind password so that it was 16 characters/digits long. This was somewhere in the banner documentation I believe.

 

File System Permission

Submitted by c-marks on Fri, 2010-03-26 11:00.

We are in the process of upgrading to Banner 8 and Luminis 4 and ran into a similar error.  It turned out that system user that the Oracle DB runs as did not have permission (at the file system level) to read the file (in the KEY_DIR entry in dba_directories table) containing the password used to encrypt the bind password on GUAUPRF.

We also found somewhere that the password length has to be a multiple of 8 characters.  This is a limitation in DBMS_OBFUSCATION_TOOLKIT.

If Luminis IV is involved, there are two defects related to SSO from Luminis to INB and SSB (only SSB is fixed).

HTH...

Chris

Syndicate content