--
- CAS gitter chatroom: https://gitter.im/apereo/cas
- CAS mailing list guidelines: https://apereo.github.io/cas/Mailing-Lists.html
- CAS documentation website: https://apereo.github.io/cas
- CAS project website: https://github.com/apereo/cas
---
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 cas-user+u...@apereo.org.
To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/7ba760c2-d0ba-4801-bc57-4c6de76f015a%40apereo.org.
The idea here is that you protect this LTPA generator REST resource by CAS, so then CAS client in front of it delegates to CAS to do authentication transaction by standard means and to make the authenticated principal available to the generator where it grabs it, generates the LTPA, stuffs it into a Cookie and redirects to a target LTPA-aware resource of choice where it can be used, validated, etc. The entire idea here is to decouple the LTPA generation business from CAS server as it does need to concern itself with it, hence the name "ltpa bridge". If you think this design is "too complex", you could of course complect the LTPA bits with the CAS server by modifying its login flow, etc. DIY programming is required in that case.
Hope it helps,
D.
On Nov 26, 2016, 08:18 -0500, Joseph Pine <jopin...@gmail.com>, wrote:
Ok I've found that already.But is there a way to connect cas directly to a external LTPA cookie generator?I already have an LTPA generator, so I would like to ask the CAS to ask the generator and authenticate the valid user.Thanks.
To unsubscribe from this group and stop receiving emails from it, send an email to cas-user+unsubscribe@apereo.org.
To unsubscribe from this group and stop receiving emails from it, send an email to cas-user+unsubscribe@apereo.org.