This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Webportal page fails to authenticate user

Hello everyone! 

Everytime I do a database transport, the OAUTH on the webportal breaks. 

Here is from the webpage:

One or more errors occurred.
Failed to authenticate user.
An error occurred while sending the request.
An error occurred while sending the request.
The underlying connection was closed: An unexpected error occurred on a send.
Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
An existing connection was forcibly closed by the remote host
Click the button below to log in as a different user.
Then from the webportals Log file this is the error it generates:
at VI.WebRuntime.VI_StandardWeb.VI_Common_Login.InitComponent(Control _parentControl, CancellationToken ct)
---> (Inner Exception #0) VI.Base.ViException: Failed to authenticate user. ---> QER.OAuthAuthentifier.OAuth2Exception: An error occurred while sending the request. ---> System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
Does anyone have a fix for this?!
  • What version of Identity Manager are you using? Does this only happen on importing a transport file or also on creating a transport file? This is not an issue that I have seen before.

  • we are on 8.0.1. 

    Well we are in the development of Identity manager and currently trying to roll it out. It just becomes frustrating when you are trying to show a user approval process, and the website never works. So there are quite a bit of changes, but all changes get funneled through me. In addition to that, i have not touched anything for the webportal after it gets fixed. Which typically happens because the Client ID goes missing, or the shared key goes missing, or the cert thumbprint goes missing, or a combination of any of those missing, but lately, even after inputting those parameters, doing a recompile, recycling services etc, it stopped being easily fixable.

  • Just to confirm are you saying that the oauth configuration parameters are getting reset after you perform a transport? 

  • 90% of the time, one of those parameters turns up missing. Very rarely will the OAUTH site break without those parameters missing. Except for the current state of our dev environment. Its currently broken and all the parameters are there. 

  • I suggest contacting support at this point.