Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Latest CasAuthenticationFilter uses different default security endpoint (/login/cas) #4

Open
cm325 opened this issue Jul 14, 2016 · 3 comments

Comments

@cm325
Copy link

cm325 commented Jul 14, 2016

I just worked through using your modifications for a new jhipster build (they were a lifesaver!!), and it wasn't working, and the problem was that the lastest spring security CasAuthenticationFilter has a different security endpoint that gets registered by default, so instead of:

/j_spring_cas_security_check

its now:

/login/cas

With so many changes coming from Spring 3, xml config, etc, it would be hard for a new user to catch this-

@jgribonvald
Copy link
Owner

Thanks for your feed back, you are right about that, an upgrade is needed
; )
Le 14 juil. 2016 19:55, "chris marx" notifications@github.com a écrit :

I just worked through using your modifications for a new jhipster build,
and it wasn't working, and the problem was that the lastest spring security
CasAuthenticationFilter has a different security endpoint that gets
registered by default, so instead of:

/j_spring_cas_security_check

its now:

/login/cas

With so many changes coming from Spring 3, xml config, etc, it would be
hard for a new user to catch this-


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#4, or mute
the thread
https://github.com/notifications/unsubscribe/ABhfY2uAM027cXpZQHJL8A_pTLi5U9tTks5qVngngaJpZM4JMr_-
.

@cm325
Copy link
Author

cm325 commented Jul 14, 2016

No problem. We've really appreciated your jhipster/cas demo, there is a real lack of documentation at the moment it seems on getting spring security configuring correctly with Java config, and of course CAS.

I'm curious, did you also look at the possibility of casifying the oauth version of jhipster, now that cas 4 has full oauth support?

@jgribonvald
Copy link
Owner

No, sorry not again... I planned to migrate our CAS from a version 3.4.12
to 4.x at the end of the year only. We wait that all feature for failover
in CAS were fonctionnal before to explore...
Le 15 juil. 2016 01:23, "chris marx" notifications@github.com a écrit :

No problem. We've really appreciated your jhipster/cas demo, there is a
real lack of documentation at the moment it seems on getting spring
security configuring correctly with Java config, and of course CAS.

I'm curious, did you also look at the possibility of casifying the oauth
version of jhipster, now that cas 4 has full oauth support?


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#4 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABhfY0zNGol4Y0MhCgBw2HdZ-zhqWUzjks5qVsTrgaJpZM4JMr_-
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants