02.09.2022
09:56
Hello, we have switched webconBPS to standalone in the last day, everything works so far but the Word add-in reports a "401" when logging into the portal.
Does anyone have an idea why the user has permissions for everything but when logging in via the add-in supposedly has no permissions?
thanks in advance
03.09.2022
09:37
Hi Phil,
these are just wild guesses. :)
1. You did change the address in the word addin?
2. Do the users have at least Metadata access privileges on application level?
https://community.webcon.com/posts/post/webcon-bps-designer-studio-privileges/44
Best regards,
Daniel
06.09.2022
10:37
Hi Phil,
these are just wild guesses. :)
1. You did change the address in the word addin?
2. Do the users have at least Metadata access privileges on application level?
https://community.webcon.com/posts/post/webcon-bps-designer-studio-privileges/44
Best regards,
Daniel
Hi Daniel,
thanks for the quick reply, unfortunately it's not the meta rights.
On a client also comes a 401 at the browser login but then it tries to call localhost:port.
On the server itself it remains with the 401.
The user is system administrator in the global webcon rights.
Best regards,
Matthias
06.09.2022
14:47
Hi Daniel,
thanks for the quick reply, unfortunately it's not the meta rights.
On a client also comes a 401 at the browser login but then it tries to call localhost:port.
On the server itself it remains with the 401.
The user is system administrator in the global webcon rights.
Best regards,
Matthias
Hi Matthias,
I have no idea, why the client would retry with localhost upon receiving a 401.
On the server you may receive the 401 due to LoopbackCheck. There are two options for this, so that you can connect to the portal on the server.
https://techcommunity.microsoft.com/t5/iis-support-blog/system-net-httpwebrequest-401-caused-by-loopbackcheck/ba-p/311210
Best regards,
Daniel
