On Tue, 16 Apr 2013, Constance Morris wrote:
Hi Andy,
Thank you! May I confirm with you if I am understanding things? What I
am wanting to do with CAS is use it for SSO authentication into our
school luminis portal and the additional resource links we provide to
students from within the portal. That way, they will not be prompted to
login to those additional resources once they have already logged into
the portal. I had been thinking about also setting up Shibboleth in
addition to CAS for a more secure SSO authentication.
Are you running Luminis 4.x or Luminis 5?
So for:
1.) I've got this based on what you said, but will CAS need to connect
via port 389 at all or just strictly 636 to the LDAPS?
I would use LDAPS (port 636) because you don't want cleartext passwords
exposed on your network.
2.) This possible database server - would that be Active Directory (AD)?
While we have the luminis portal LDAP - we use Active Directory LDAP as
our means of authentication currently into our luminis portal.
Active Directory is an LDAP server, not a database server. I'm not sure
which LDAP server you should use. If you want to integrate with Luminis,
then you probably want to use the same LDAP server that Luminis uses for
authentication.
3.) What about port 8447 - I don't know the difference between the two
but I've heard someone mention that one before for HTTPS type access.
Would this be the same for other resources besides D2L like
AdvisorTrac?
I'm not sure. What service listens on port 8447?
4.) This is where I think someone mentioned port 8447 or 8090.
If you are bringing up a new CAS server, I recommend using the standard
HTTPS port (443) rather than something unusual.
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
