Using OAuth on On Premise Orchestrator fails with Scope defined in HTTP Parameters

[monkeymalle]

Hi

I have created an Application on our On Premise Orchestrator 2021.10.3 and wanted to login from "Orchestrator Manager" using OAuth.
When I used the generated Client Id and Secret, then the login failed.
I used Fiddler to track the parameters sent to Orchestrator and saw the following Response:

---

{"error":"invalid_scope"}

---

I then saw that Orchestrator Manager sends the scope as a parameter:

---

OR.Monitoring OR.ML OR.Tasks OR.Analytics OR.Webhooks OR.Folders OR.BackgroundTasks OR.TestSets OR.TestSetExecutions OR.TestSetSchedules OR.TestDataQueues OR.Audit OR.License OR.Settings OR.Robots OR.Machines OR.Execution OR.Assets OR.Administration OR.Users OR.Jobs OR.Queues

---

I then created the same User/Application Scope on my Application in Orchestrator, but the login still failed.

After that I located the HTTP Request in MakeAuthenticationRequest_OnPremises.xaml and removed the "scope" parameter.

Now the OAuth worked and I can use the On Premise Application I created.

Best Regards Martin

[ethbr0-uip]

@monkeymalle Believe this might be running up against an "excessive number of scopes specified" bug that was fixed in 2022.4.x

If so, then shortening the list of scopes specified resolved the "invalid_scope" response. Or, as you noted, omitting scope