What I would suggested doing: getting to the point where you have received the 401s, open up your dev tools(f12) console and then issue: you should then get a result that corresponds to your authenticated users SFB status. I believe this perception is made more likely due to subsequent issues with the chat client (which I currently haven't got to the bottom of). The above would explain why this appears to be intermittent, if a the client is already authenticated, then you will not see the redirect and will not see a 401 in dev tools. SDK sees 401 and redirects to auth using the token previously obtained.I think that the 401 response you see are expected. I thought I was having the same problem but everything was actually working correctly. If someone have an idea you are welcome to have you found anything or know what is the cause of this behaviour? I still don't know the reason for why it is working only this way. Now I can successfully login using Skype WebSDK. And also changed reply url to And very strangly but it helped. Of course I was setting the reply url accordinly as Then I tried to move everything in skype directory to the root - to the htdocs folder. I was trying to run the index.html page on the localhost in the htdocs/skype directory. And again no luck, the same error - 401 - Unauthorized: Access is denied due to invalid credentials. Then I updated config.js in the skype web sdk simple sample for SfB online application. Then I registered the new app in Azure Active Directory to use Skype for Business. Associated my O365 account with Azure AD as described here. Created a Microsoft account, got a free O365 tenant, signed up for free Azure Active Directory trial account. I did everything from scratch following the guide here. "userConsentDisplayName": "Access ringmd-test", "userConsentDescription": "Allow the application to access ringmd-test on your behalf.", "adminConsentDisplayName": "Access ringmd-test", "adminConsentDescription": "Allow the application to access ringmd-test on behalf of the signed-in user.",
0 kommentar(er)
