Looking for suggestions:

I want to protect access to an application via a password. I want the password to automatically change daily. I want the application to be able to determine today's password without having to read it from an external source (i.e., algorithmically/programmatically derived). This last requirement means:

o no special profile with password changed daily
o no validation list use
o no encrypted password stored in external object such as *FILE or *DTAARA

I envisage:
o Application objects are *PUBLIC *EXCLUDE
o Application objects are authorised to a specific group profile
o Password generator is *PUBLIC *EXCLUDE
o Password generator is authorised to a specific profile (different from the above)

In actual use a user who is a member of the application group AND who needs to use this particular application will request the password from an authorised issuer. The issuer will use the password generator to determine today's password. The user will then use the application.

The "automatic daily change" requirement means the password generation/ validation is tied to the date but obviously simple encryption linked to the date will not be very secure nor will each daily password be sufficiently different from the previous one.

I have some ideas but thought I would see what others suggest--always presuming you think this sufficiently interesting to bother with :)

Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists

http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------




This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].