Authentication fails if key contains special characters #40

Alanwe · 2017-01-12T11:17:08Z

The Authentication Key generated by Azure AD sometimes contains reserved characters which causes a 401 error when authenticated when passed in the authentication body

Validated error using Key <- URLencode(Key, reserved = TRUE) which then resulted in a successful 200.

Add URLencode by default into the Authenticate function

* master: add updated docs namespace and description add rstudio-server tag for rserver hdI fix error message display fix and tests for rserver hdi clusterVersion fix and add r-server and edge node options camel case fix and add alias for AzureListRG fix `AzureListRG` -> `azureListRG`; camel case change in function name #40 ENCODE the client secret to avoid occasional 401 Added Scale Sets functions Deploy Template handle FAIL condition Added 3 functions for ScaleSets Fixed Deploy template to manager FAILED status

Alanwe self-assigned this Jan 12, 2017

Alanwe added the bug label Jan 12, 2017

Alanwe added a commit that referenced this issue Jan 12, 2017

#40 ENCODE the client secret to avoid occasional 401

8a9c28d

andrie changed the title ~~Azure Authenticate Issue~~ Authentication fails if key contains special characters Feb 6, 2017

andrie added this to the v0.2.3 milestone Feb 6, 2017

andrie closed this as completed May 21, 2017

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Authentication fails if key contains special characters #40

Authentication fails if key contains special characters #40

Alanwe commented Jan 12, 2017

Authentication fails if key contains special characters #40

Authentication fails if key contains special characters #40

Comments

Alanwe commented Jan 12, 2017