Login Requests
Planview Advisor provides an authentication token to use in API calls. This token can encode a subnet mask to limit the requests using the token to only a specific set of IP addresses. Please let us know which IP address/subnet the requests of the ETL will come from if you are interested in IP masking for querystring-authenticated calls.
A new token will be issued every time the IP address needs to be changed or upon change of password for the ETL user. A system administrator is able to issue the tokens. The most efficient way to run Advisor REST API calls is to first authenticate with an HTML login request.
Example Request URL
https://<URL>/login.aspx?username=<user_querystring_token>
Example Response
The response to this request will contain a session code cookie.
sfc_rnd_code=code=<fcad074f-2f2f-4327-9a7b-93c035da609a> (in brackets is an example for such a code)
If the session code and the ASP.NET session id are included in the headers of the consecutive requests, the call will be authenticated by the session user and the requests will be processed slightly faster. Otherwise, include the authentication token in each call (the format of which will be explained below) and then each call will authenticate separately based on the token. In the latter case the login call is unnecessary. Each call is authenticated separately.