Dear Community,
I have a question regarding the change from Basic Authentication to Modern Authentication aka OAuth 2.0 on Polycom Trio devices.How can I tell from the Web Interface GUI or from the device log files if the Trio does OAuth or not?
Things I did so far:
1) Approved the consent URL in Azure signed in as tenant admin
2) updated the device to firmware version "5.9.2 Rev AB"
I logged in to the web interface gui and checked Diagnostics -> Skype for Business Status -> Skype for Business Parameters" and I get following parameters.
User Certificate Fetch Status | Got User Certificate |
Web Auto Discovery User Location | External |
Web Auto Discovery FQDN | sipfed1E.online.lync.com |
Certificate Valid from | Mon Mar 2 09:44:33 2020 |
Certificate Valid up to | Mon Mar 2 17:44:33 2020 |
Skype for Business Environment | Skype for Business EnvNone |
Skype for Business O365 Status | Disabled |
Certificate Valid Until | 27901 seconds |
Certificate Validity Duration | 28800 seconds |
Certificate Exists | Yes |
Certificate Expired | No |
Credential Type | None |
Certificate Provisioning Service URL | Not Configured |
Web Ticket Service URL | https://webpooldb41e17.infra.lync.com/WebTicket/WebTicketService.svc |
Web Ticket Proof URL | https://webpooldb41e17.infra.lync.com/CertProv/CertProvisioningService.svc/WebTicket_Proof_SHA1 |
Root Certificate Chain URL | |
Web Ticket Server Pin Auth | |
Web Ticket Server Certificate Auth | https://webpooldb41e17.infra.lync.com/WebTicket/WebTicketService.svc/cert |
Federation Data Mex URL | http://nexus.microsoftonline-p.com/federationmetadata/2006-12/FederationMetaData.xml |
Update Server Internal URL | https://sippoolDB41E17.infra.lync.com:9999/RequestHandler/ucdevice.upx |
Update Server External URL | https://webpoolDB41E17.infra.lync.com:443/RequestHandlerExt/ucdevice.upx |
OAuth Token Validity in seconds | 3599 |
OAuth Token Expiry Time | Mon Mar 2 13:37:04 2020 |
Is there any indication (e.g. OAuth Token Validity and Expiry Time fields) that OAuth 2.0 authentication was done successfully? The device can initiate, start and join Skype for Business meetings.
Alternatively, is there any indication in the device's admin display, if OAuth 2.0 was applied successfully?
Thank you in advanced.
Regards,
Torsten
Solved! Go to Solution.
Hello @CyPh3R ,
Welcome to the Poly Community.
The phone would show this in the log:
042632.367|auth |2|00|prepareOAuth2TokenRefreshReqBody: ClientID:a850aaae-d5a5-4e82-877c-ce54ff916282
when you set Settings > Logging > Module Log Level Limits > Auth Service > Event 2 as the logging level.
The above is the "new" Poly App ID.
Previously we would have shown:
0731075616|auth |2|00|prepareOAuth2TokenRefreshReqBody: ClientID:131c22db-3591-4fc8-a305-55444fa5ccd3
Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.
Best Regards
Steffen Baier
If official support is required please check how to phone or open a case here
----------------Hello @CyPh3R ,
Welcome to the Poly Community.
The phone would show this in the log:
042632.367|auth |2|00|prepareOAuth2TokenRefreshReqBody: ClientID:a850aaae-d5a5-4e82-877c-ce54ff916282
when you set Settings > Logging > Module Log Level Limits > Auth Service > Event 2 as the logging level.
The above is the "new" Poly App ID.
Previously we would have shown:
0731075616|auth |2|00|prepareOAuth2TokenRefreshReqBody: ClientID:131c22db-3591-4fc8-a305-55444fa5ccd3
Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.
Best Regards
Steffen Baier
If official support is required please check how to phone or open a case here
----------------Hello @SteffenBaierUK ,
you made my day.
I checked the Trio Event 2 logs for the mentioned entries and found these pattern:
0303065436|auth |2|00|prepareOAuth2TokenRefreshReqBody: ClientID:a850aaae-d5a5-4e82-877c-ce54ff916282
I compared the entries of this Trio phone to another one we host at our office site and which is running an older firmware. This one shows:
0303070459|auth |2|00|prepareOAuth2TokenRefreshReqBody: ClientID:131c22db-3591-4fc8-a305-55444fa5ccd3
Thank you very much for sharing this quite valuable information.
Regards,
Torsten