Re: Odd behavior with profile handle switching

["Carel Teijgeler" <coteijgeler@xxxxxxxxx>]

David,

A couple of years ago I looked into those profile swap API's. IIRC you must 
have *USE rights to a user profile to access it. So grant user A *USE authority 
on the QSECOFR user profile.

I was assigned some place and belonged to the group *SECOFR and without knowing 
or passing a password I could swap to the user profile QSECOFR. To do this you 
have to be at least in the same userclass as the profile you would like to swap 
to.

Regards,
Carel Teijgeler

*********** REPLY SEPARATOR  ***********

On 29-5-03 at 14:39 David Gibbs wrote:

>I ran into some odd behavior with user profile handle switching the other day.
>
>Program X is owned by QSECOFR and adopts authority.  This program switches
>it's user profile handle to "B" midstream, does stuff, and switches back to 
>the original handle.
>
>User profile A is class *PGMR.
>User profile B is class *PGMR and in the QSECOFR group.
>
>If user profile A runs program X I get a CPF2217 error, Not authorized to
>user profile QSECOFR, when we are trying to switch to profile B.
>
>When we remove profile B from the QSECOFR group, it appears to work fine.
>
>My thinking is that somehow the fact that the users class and group are
>contradictory might be causing some problem.