Is there a limit on Token requests by user over time?

525
1
Jump to solution
12-12-2013 07:30 AM
QuinnKorbulic1
New Contributor III
Hello,

We're generating tokens programmatically using code similar to what is suggested in the Silverlight API help:

string tokenService = "http://hostname/ArcGIS/tokens?request=getToken&username=test&password=my.password&expiration=30"; System.Net.WebRequest request = System.Net.WebRequest.Create(tokenService);                              System.Net.WebResponse response = request.GetResponse();                              System.IO.Stream responseStream = response.GetResponseStream();                              System.IO.StreamReader readStream = new System.IO.StreamReader(responseStream);                              theToken = readStream.ReadToEnd();


Sometimes this generates the token successfully but other times we receive an unauthorized error. Using the tokens request page "http://hostname/ArcGIS/tokens" with the same user results in the same behavior.

Is there a limit on the number of tokens a single user can request during a specific time period? If not, why do token requests work sometimes and not others?

Thanks.
0 Kudos
1 Solution

Accepted Solutions
QuinnKorbulic1
New Contributor III
Problem solved:

We're working in an ArcGIS Server site configuration with two machines on a Domain account. The Domain account password had expired and was only reset on one of the machines in the site. When a token request was initiated, the machine where the password was reset returned a valid token and the machine where the password was not reset returned an unauthorized message. This is why we were getting (seemingly) random unauthorized messages. Once the password was reset on both machines only valid tokens were returned.

qpk

View solution in original post

0 Kudos
1 Reply
QuinnKorbulic1
New Contributor III
Problem solved:

We're working in an ArcGIS Server site configuration with two machines on a Domain account. The Domain account password had expired and was only reset on one of the machines in the site. When a token request was initiated, the machine where the password was reset returned a valid token and the machine where the password was not reset returned an unauthorized message. This is why we were getting (seemingly) random unauthorized messages. Once the password was reset on both machines only valid tokens were returned.

qpk
0 Kudos