Tickets :: Comment on [#11924] Add API in Horde_Registry

* Your Email Address
* Spam protection	Enter the letters below: .___..___.__ .___.. . \| [__ [ __ \| \|__\| \| [___[_./ \| \| \|
Comment	> Add an API in Horde_Registry_Application (Horde_Core) which changes > auth credentials and tells apps to reauthenticate with the new > credentials, ignoring cached sessions and credentials. This is needed > for IMP and gollem in some scenarios. > > cf Horde_Registry_Application#changeLanguage() for similar functionality. > > michael slusarz said: > > With our package structure, this is now something that can be added > to the Core functionality without requiring a new major release. If > implemented via a Registry_Application call, this will bump the > Registry API. But it's not BC breaking, since you can update > Horde_Core without updating applications and it won't break anything > (it won't do anything either, but that's not relevant for this > discussion). > > It does make sense to implement in this matter. Not a big deal if > one of these more untested apps (passwd) requires something other > than a x.0 install anyway; in other words, I'm suggesting that this > sort of registry change is most appropriate to add to IMP 6.1. > There's still some limitations though: any user defined code in an > init hook won't be triggered if the password changes. That is > something that can't really be addresses until the next major Horde > release. > > In other words - the best/cleanest solution is probably to instead > require that if the password changes, the Horde session is destroyed. > IMHO, this is not asking too much: password changes are fairly rare, > it prevents all possible authentication problems, and this is not an > alien concept to users since all sorts of websites require > re-authentication when the password changes. > > michael > >
Attachment
Watch this ticket

Saved Queries