Upgraded to Banner 8, sso to banner not working
Over the weekend we upgraded to banner 8, and now the sso links in luminis won't work. I'm getting the Unsupported OID Error. Has anyone who has gone through the upgrade ran into this problem? We double checked the ldap password, double checked all the parameters in banner, but can't spot the problem. Nothing changed on luminis, only banner was upgraded.
Auth method
Which authentication method are you attempting to use? Hopefully the new "midtier" method. :)
Check out what is returned from the configurls for your banner system (ie: es.sctssb.configURL and es.sctinb.configURL ) when you append "?oid=1" to the end of those URLs.
Todd
GUAUPRF
If you haven't already, might want to review the LDAP tab on Banner form GUAUPRF, it has an entry there for LDAP and SSO and a place to input a password for the Directory Manager user. We just went through a password-change exercise and had to update Banner there to make that same error go away.
Something obvious perhaps
At our institution, we change all of the schema owner and service accounts to their default values, perform the banner upgrades, and then change the accounts back to their original values once the upgrade is complete. Assuming you follow similar procedures, could the password to banproxy possibly been changed or the account locked out??? Is it both SSB and INB that the SSO is broken? What about banner channels?
cptool sync password
Once I ran cptool sync password and restarted the system, the sso to self service banner worked. We don't use the sso to inb for security reasons, so I didn't bother testing that.
We still don't have the banner channels working yet, I placed all the new cars in the directory. All the channels are coming up blank, nothing too detailed in the cp.log file either.
Re-enter GUAUPRF passwords
After upgrade to Banner 8.2 SSO (mid-tier, sctssb) did not work with 'Unsupported OID service' error.
One of the accompaning changes was moving Oracle to UTF-8. Our DBA thought that the encrypted password for Directory Manager as stored in GURUPRF didn't survive the transfer to UTF-8, so we re-entered the password in the form and restarted the portal (as well we did >cptool sync password, this may or may not have had an effect).
After restart, SSO worked. We think it was re-entering the pasword in GUAUPRF that made the difference.
Bob
Luminis IV.x, Banner 8 and SSO
We also had the same issues after upgrading to Banner 8. Some other issues were also not able to connect to the following urls:
https://self-serve.fuller.edu:4445/prod/gokssso.P_GetConfigVersion2_sserv
https://self-serve.fuller.edu:4445/prod/gokssso.P_GetConfigVersion2_sserv?oid=123
We followed the instructions posted by Bob (Re-enter GUAUPRF passwords) and the SSO worked!
Thanks Bob!
Thelma