On 12 April 2013 14:56, Ejarque, Juan (NSN - ES/Madrid) <
juan.ejar...@nsn.com> wrote:
>
> I’d like to ask your help to develop a fix/enhancement of OpenNMS for the
> following issue:
>
> *The openNMS p**ass**w**ord** is compliant with encryption requirements**,
> but th**e only problem is that it doesn't have a maximum expire time,
> that needs to be implemented according to general security policies.*
> *The request is that the **password must remain **valid for a maximum of
> 90 days** from when it was last changed**. So, there must be a** **
> password** expiration time of 90 days**.*
>
>
Hi Juan,
Have you thought about tying OpenNMS into a centralised authentication
platform, such as LDAP or RADIUS, and letting the centralised platform take
care of password expiration etc?
This is currently possible, you can find some documentation here:
http://www.opennms.org/wiki/Spring_Security_and_LDAP
http://www.opennms.org/wiki/Spring_Security_and_Radius
Not what you are looking for, but may fit your requirements if you already
operate such a system!
Regards,
Dave
------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ
opennms-devel mailing list
To *unsubscribe* or change your subscription options, see the bottom of this
page:
https://lists.sourceforge.net/lists/listinfo/opennms-devel
