W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > June 2018

Re: [webrtc-pc] Refine error reporting for identity assertion

From: ekr via GitHub <sysbot+gh@w3.org>
Date: Tue, 19 Jun 2018 03:56:08 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-398266756-1529380567-sysbot+gh@w3.org>
There are a huge pile of IDP errors already defined:


idp-bad-script-failure | The script loaded from the identity provider is not valid                 JavaScript or did not implement the correct interfaces.
-- | --
idp-execution-failure | The identity provider has thrown an exception or                 returned a rejected promise.
idp-load-failure | Loading of the IdP URI has failed. The                 httpRequestStatusCode attribute is                 set to the HTTP status code of the response.
idp-need-login | The identity provider requires the user to login. The                 idpLoginUrl attribute is set to the URL that                 can be used to login.
idp-timeout | The IdP timer has expired.
idp-tls-failure | The TLS certificate used for the IdP HTTPS connection                 is not trusted.
idp-token-expired | The IdP token has expired.


I think this can be closed.

GitHub Notification of comment by ekr
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1314#issuecomment-398266756 using your GitHub account
Received on Tuesday, 19 June 2018 03:56:10 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:44 UTC