xpra icon
Bug tracker and wiki

This bug tracker and wiki are being discontinued
please use https://github.com/Xpra-org/xpra instead.


Changes between Initial Version and Version 1 of Ticket #2261, comment 16


Ignore:
Timestamp:
05/07/19 06:13:28 (2 years ago)
Author:
Antoine Martin
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #2261, comment 16

    initial v1  
    1010}}}
    1111That's because the authentication is being forwarded to the html5 client, but it's using the capabilities which were supplied by the proxy server..
    12 The html5 client didn't handle sha512: [https://github.com/digitalbazaar/forge/issues/401 hmac does not allow for use of sha512], so I've updated the [https://github.com/digitalbazaar/forge] library to the latest version and things work fine now.
     12The html5 client didn't handle sha512: [https://github.com/digitalbazaar/forge/issues/401 hmac does not allow for use of sha512], so I've updated the [https://github.com/digitalbazaar/forge] library to the latest version in r22650 and things work fine now.
    1313
    1414A more correct solution would be to figure out in advance if the proxy will be handling the authentication itself or if it will forward the challenge to the client, and set the authentication capabilities accordingly. But that's just a lot harder than making sure that both proxy and client have the same capabilities.