I also see a record of it in the Okta Admin console. The signon works great, and all the triggers work to indicate the user is successfully logged in. I'm using terraform v0.13 and ad version is v1.6.0, azuredevops version is v0.1. I’m creating a new Angular app and using the Okta embedded signon widget. Difatti l’errore 401, in alcuni casi, tende a sparire da solo mostrandoti nuovamente la pagina corretta di accesso al tuo sito web. Si tratta di un errore temporaneo che, a differenza dell’errore http 403 si risolve con piccoli accorgimenti. However this raises a prompt even if the auth token is correct: Set JsonBag PBConfig.CloneItem ('CreatePushJson') Make a deep copy of template JSON. In light of information below I tried sending the auth token as a user ID value. I've used the same ClienID/Secret key which I've generated a few seconds ago.Ĭould anyone able to help here? Error message.Įrror: getting authenticated object ID: Error listing Service Principals: autorest.DetailedError Questo errore ti dice che potrai accedere ma cambiando credenziali, ovvero utilizzando quelle corrette. If the prompt is canceled by the user then the 401 gets reported to the code. I've been getting 401 error when trying to authenticate my registered application in Azure AD from azuredevops pipeline using terraform.