Hi Vlastimil,

Other group members my have more ideas, but I would say the most
common approach is to keep the administrator credentials in a
configuration file (or in the code even).  A slightly more secure
approach would be do the same for an auth token instead of the
administrator credentials.

Another fairly common approach is to keep the administrator
credentials in memory.  For example, when you run the script, have it
prompt for credentials.  In your program, remove any references to the
credentials after obtaining the auth token.

Unfortunately there is no way to circumvent the requirement to
regularly update the token, since they expire.  And in order to get a
new token, you need send the correct credentials to ClientLogin.
Admittedly, these limitations make it difficult to have scripts run
completely unattended without persistent credentials.

You can create another administrator for use with the Provisioning
API.  In fact may administrators do this.  However for Premier Edition
domains, you would have to pay for this user just like a normal user.

-alex

On Mar 6, 2:02 pm, Spes <[EMAIL PROTECTED]> wrote:
> Hi,
>
> as I look at the Provisioning API, admin user authentication (time
> limited token) is needed.
> I need to use the API in non-interactive scripts without storing my
> credentials in there or
> regularly updating token. Is there any way how to reach that, e.g. by
> creating dummy admin.
> (non-paid) user or other authentication method?
>
> Thank you for any help,
> Vlastimil Holer
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Apps APIs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/google-apps-apis?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to