Seems like it will work fine for what you want to do.  Create your auth
form, which has $ USER$ as the username and a password field (fid 102) where
they can enter the password, perform the rp in an AL and pass the password
field.  If you are using an area plugin for auth, it should be handed off to
the plugin.

Axton Grams

On Wed, Sep 3, 2008 at 10:07 AM, ARS Dummie <[EMAIL PROTECTED]> wrote:

> ** Joe,
>
> I think this will not help us. Let me try to make it clearer:
> We want to force the user to authenticate again before he is approving
> changes.
> Means that the user logs into the system with SSO (via Remedy User oder
> Mid-Tier) and then later on if he wants to approve a change he has to
> authenticate himself again by entering again his login name and password in
> a dialog that pops up after he clicked on the 'Approve' button.
>
> Hope this makes it clearer.
>
> Thanks,
> Dan
>
>
> __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
> html___
>

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"

Reply via email to