Authorization resoluiton process

[Former Member]

Hi,

Can you please let me know the "process" involved ( I know its different from corporation to corporation ) once a authorization failure is observed.

thats to say what is the process( route for example -mail to manager ) taken to resolve the authorization process from the failure to resolution and cofirming the resolution to the end user.

PS:I am not looking answers on for SU53 or ST01

Thanks

[Former Member]

Hi George,

I report the missing authorization or (as in most cases) the excessive authorization to our global authorizations virtual community. For this we have a support email address.

To ease the process, some systems have a virtual system where the problem can be replicated (refresh takes about 1 hour) and debugged in an isolated environment without disturbing production. This is either done by some support person, or other environments I can debug myself based on trust (display only) - but I dont want that in production... I have a ticket open for that as well.

I then get a ticket number which I can use as a reference to follow the request.

This application works well, because I can always access the current status of the ticket.

This takes about 2 years on average, during which time I receive occational emails from the ticketing system with the message type "Degredation of service for 1 user" when the ETA is extended by someone called WF-BATCH.

(During which time I find plenty of work-arounds).

Just a pinch of salt...

Good question!

Julius

[Former Member]

Hi Julius !

Great ! I have the following questions on this answer now:Primarily because I am not an expert as yet !!

1. The last sentence"This takes about 2 years on average, during which time I receive occasional emails from the ticketing system with the message type "Degredation of service for 1 user" when the ETA is extended by someone called WF-BATCH." I did not understand . can you please throw more light !!

2. If an end user lacks an authorization, whats the process that you would follow to grant him the same.

Looking forward to hear from you.

Thanks

[Former Member]

Hi George,

What I meant (in one sense) is that it will often take longer to implement a change, than what it will to find a solution for an individual user.

This will be largely dependent on how you have implemented your authorization concept.

What I meant (in another sense) is that authorization admins are sometimes far removed from the busines processes (and the development work), so when a request for a change hits the authorizations group, then the business and developers find it odd because it was not forseen that authorization problems should occur during normal operations.

Can you relate to that?

Cheers,

Julius

[Former Member]

Well explained !! Thanks a Ton.

[Former Member]

No doubt these processes and the security design are most challenged when a restriction is requested.

Hopefully others will still contribute their experiences / solutions.

Cheers,

Julius