Time based User ID.

[Former Member]

Hi

My Requirement is,

Our users are working on Shift basis in Plant. (8 hours per shift).

they have one userid assigned to one person per shift {3 Person per day = 3 shift}

I need to assign three different password to same user id. It means one password expire every 8 hours and generate new password or asked for new password every 8 hours.

Is it possible ?

Please advised.

Regards

Jayesh

[Former Member]

Why don't you just give them 1 ID each?

Your requirement is not possible without customising.

[Former Member]

Hi Alex,

Thanks for your quick reply.

but we dont want to do that for some reason.

Regards

Jay

[jurjen_heeck]

> Thanks for your quick reply.

> but we dont want to do that for some reason.

Maybe if you give us your reason we can help you find a solution.

[Former Member]

There are a number of threads here at SDN about this... Most of them tend to address the symptoms and get bogged down in them, instead of finding usefull solutions.

The advice which Alex has given is one I would agree with, generally.

But perhaps you are refering to another problem related to the terminal itself?

Please take a carefull read through these three threads to see your user ID related options with ABAP passwords and why these are intentionally not a solution if the system is configured and used correctly...

-

-

-

What you might be interested in, is solutions which other companies use to provide ESS (Employee-Self-Service) solutions to folks who do not have access to a PC as part of their normal work.

For this, you can physically secure the terminal and logically it's operating system via engineering, and use a Single-Sign-On solution to log each user onto the SAP application if they authenticate against your comany network first. It is then the responsibility of the person before them to log off from the application (but not the terminal).

As Jurjen correctly asked, your need to provide more details of your requirement.

Additionally you can use biometrics and smartcards and all sorts of things on the client side (with the physical terminal) if this enables an authentication against the backend system. This would be more specialized, but possible.

If it does not your requirement, then you need to use generic access as a next-best (but still not not least-worste... ) option however you might have audit problems...

There are a lot of design considerations in this, and SAP will only make some of them possible (as far as I have observed) otherwise they could be misused...

Cheers,

Julius

Edited by: Julius Bussche on Mar 2, 2009 12:40 AM

[WolfgangJanzen]

>

> Our users are working on Shift basis in Plant. (8 hours per shift).
> they have one userid assigned to one person per shift {3 Person per day = 3 shift}
> I need to assign three different password to same user id. It means one password expire every 8 hours and generate new password or asked for new password every 8 hours.

This is no good idea - for many reasons:

1. auditibility (critical, if multiple users share one account)

2. usability (changing passwords every 8 hours leads to frustration)

3. license issues (PS: an "ordinary" employee is supposed to work also about 8h per day, so there is no reason to state that your shift workers are "lightweight" in terms of license user classification)

Please create one account for every user.

Then, they can use their own password (which they are supposed to treat as personal secret) - and they can utilize all personalization features offered by the system. Since every user is then using his/her own account, it will be possible to track all changes (via change records) undertaken by that person (-> accountability / auditibility).