Yes we created the the UDCid. I guess the problem we are having is that the CAS is not sending the UDCID that is stored in the AD. How do I configure CAS to pull the UDCID. Thanks for your response in advance. Your help is really appreciated. -Alex Adao
On Tue, Aug 14, 2012 at 6:36 PM, Andrew Morgan <[email protected]> wrote: > On Tue, 14 Aug 2012, Alexandre Adao wrote: > >> Hello, >> >> I am running BANNER ENTERPRISE IDENTITY SERVICES (BEIS) 8.1.5 and CAS >> (Jasig Central Authentication Service 3.4.10). >> The SSO Manager acts as a front-end to SSB, bypassing native SSB >> authentication. CAS handles the authentication with no problem. SSB is >> accessed through one of the URL: >> ttp(s)://<host>:<port>/ssomanager/c/SSB. After the user >> authentication, I am having the following error on the SSO Manager >> server. >> >> Error >> com.sghe.sso.exception.ApplicationException: UDC Id not available >> >> Can anyone help me on this one, please? what am I missing? > > > Did you create UDCIDs for all your SPRIDEN users yet? The table GOBUMAP > contains a mapping of UDCID to PIDM. Also, I think your CAS server needs to > release the UDC_IDENTIFIER attribute to SSO Manager, which it then uses to > lookup the PIDM in GOBUMAP. > > Sorry, I'm a little fuzzy on the details because it has been a while since > we set this up. > > Andy > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
