You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now I'm having a problem logging in with STI models. My app has 3 different model namely User, Staff, and Admin. User is the base model. Every model has different scope to access.
Currently, only User is able to sign in using CAS. The other is having problem after logging in at the CAS server. For Admin & Staff models the app return Invalid Email & Password error after signing in from the CAS server.
I believe this has something to do with the file lib/devise_cas_authenticatable/strategy.rb. I just can't figure out where is the problem really is.
Anyone has clues or leads on this problem.
The text was updated successfully, but these errors were encountered:
Hi Ariff, so sorry for not getting back to you until now!
If you're getting the Invalid Email & Password message, that sounds like the CAS strategy isn't being triggered at all (because that message comes from the database_authenticatable strategy). My guess would be that the valid? method is returning false.
Like you, I'm not sure why this would be the case, but maybe what's going on is that your model subclasses aren't inheriting the authenticate_with_cas_ticket method from the mixin. Can you make sure that all of the subclasses have that method?
Right now I'm having a problem logging in with STI models. My app has 3 different model namely User, Staff, and Admin. User is the base model. Every model has different scope to access.
Currently, only User is able to sign in using CAS. The other is having problem after logging in at the CAS server. For Admin & Staff models the app return Invalid Email & Password error after signing in from the CAS server.
I believe this has something to do with the file lib/devise_cas_authenticatable/strategy.rb. I just can't figure out where is the problem really is.
Anyone has clues or leads on this problem.
The text was updated successfully, but these errors were encountered: