Hello,
I am working towards a functional REST login. Using the documentation and
examples, I was able to put together a proof of concept in php, that logs in to
CAS, retrieves an unencrypted TGT which can’t be validated.
How would you validate it?
BQ_BEGIN
Since the TGTs are configured to be encrypted, I assumed I’d be getting an
encrypted TGT back, so I could set a cookie that would facilitate SSO
authentication.
When I log in to CAS via the CAS delivered login, my browser receives a cookie
called TGC that is encrypted, I assume this is the encrypted TGT.
BQ_END
No, it isn't.
BQ_BEGIN
What am I missing? Guidance is greatly appreciated.
BQ_END
Nothing. This is functioning as designed.
There is the ability to encrypt tickets that are shared with the rest of the
world but one, that has nothing to do with the cookie, two it's an auxiliary
feature and finally, there isn't anything you can do with it on the app front.
It's also entirely likely that rest API doesn't support the usual ticket
encryption functionality, but since you don't mention what CAS version, (sort
of an important detail) I can't say for sure.
-- Misagh
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
---
You received this message because you are subscribed to the Google Groups "CAS
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/a/apereo.org/d/msgid/cas-user/310591097.4326952.1503584932377.JavaMail.zimbra%40unicon.net.
