| Project: | Integration of Scheduling component UniTime (University Timetabling) with CAS Campus |
| Component: | Code |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
UniTime uses MD5 encoding and finally encodes the byte array in Base64 format. CAS uses a PlainTextPasswordEncoder which does not encode the password. There is another encoder in CAS called DefaultPasswordEncoder. I'm not sure if this encodes the password in the same format as UniTime although it used MD5. So i was thinking if we could add our own password encoder in CAS similar to the one in UniTime.
#1
By sandyAll alternatively consider SHA. In any case the type of encoding should be plugable with the default for CAS left as it is. The key part of integration would be for UniTime to call CAS for the Token and not deal with passwords at all. Decoupling is perhaps an important step towards security.