Schlagwörter: oauth2 401 Unauthorized perform post
Ansicht von 1 Antwort-Thema
-
AutorBeiträge
-
-
11. August 2022 um 14:14 Uhr - Views: 522 #13547
Hello,
I am trying the oauth2 plugin to overcome the MS limitation planned for end of Sepember, but I am struck…
- I registered an application in Azure
- I setup a redirect URI to the local IP (since it’s not published) : https://172.22.20.226:8443/otobo/index.pl?Action=AdminMailAccount
- I assigned the DELEGATED API permissions with ADMIN CONSENT
-
email
IMAP.AccessAsUser.All
offline_access
POP.AccessAsUser.All
SMTP.Send
User.Read
-
email
- I created the SECRET
- I modified the Povider inserting my tenant id
I am still getting errors…
Wed Aug 10 14:20:12 2022 (Europe/Rome) error OTOBO-CGI-11 Could not request access token
Wed Aug 10 14:20:12 2022 (Europe/Rome) error OTOBO-CGI-11 Got: ‚401 Unauthorized‘!
Wed Aug 10 14:20:12 2022 (Europe/Rome) error OTOBO-CGI-11 Can’t perform POST on https://login.microsoftonline.com/4d0aca28-2980-409e-8efa-7351d66d1be2/oauth2/v2.0/token: 401 UnauthorizedAny idea on how to debug this problems ?
Thanks,
Massimo
-
11. August 2022 um 14:28 Uhr #13548
As in the best tales, I discovered the error just after posting the thread.
For others: when you create the application:
- must be a „WEB“ application type
- you must select ONLY „ID TOKEN“, and NOT „ACCESS TOKEN“, and NOT BOTH
-
-
AutorBeiträge
Ansicht von 1 Antwort-Thema
- Das Thema „ Question: how to debug „Got: ‚401 Unauthorized‘!““ ist für neue Antworten geschlossen.