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

Deal with inactive or frozen account #204

Open
shenhf opened this issue Mar 11, 2014 · 2 comments
Open

Deal with inactive or frozen account #204

shenhf opened this issue Mar 11, 2014 · 2 comments
Labels
Milestone

Comments

@shenhf
Copy link

shenhf commented Mar 11, 2014

Is there any solution to deal with inactive accounts at casserver side?

@mitfik
Copy link
Contributor

mitfik commented Mar 12, 2014

It depends on what exactly are you asking for.
If you are asking about authenticators, if they can deal with additional conditions then it is up to that particular authenticator.
For example in ldap authenticator you have that possibility to define filter like: filter: (active=yes) which will check additional if the field active is set to yes.

If you are asking about sending proper error message (no matter what authenticator you will use) to the user that the credential are good but your account is not active then no, CAS do not have support for that.

@mitfik mitfik added the feature label Mar 12, 2014
@mitfik mitfik added this to the rubycas 2.0 milestone Mar 12, 2014
@shenhf
Copy link
Author

shenhf commented Mar 13, 2014

Finally I hacked casserver/lib/casserver/authenticators/sql_bcrypt.rb, hard coded matching_users method. It stopped inactive user login, as you said, not sending proper error message.

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

No branches or pull requests

2 participants