Ok, I missed to tell you that I already read a lot of pages .. but non described if the "WWW-Authenticate: Negotiate" mechanism is supported, like described here:
https://tools.ietf.org/html/rfc4559
My latest test with a locally .net core kestrel server with NegotiateDefaults.AuthenticationScheme seems to be ok,
when I adress localhost.
http://localhost/api/sample/secured
I get these ResponseHeaders
HTTP/1.1 200 OK
Date: Mon, 30 Nov 2020 16:58:58 GMT
Transfer-Encoding: chunked
Content-Type: text/plain; charset=utf-8
Server: Kestrel
WWW-Authenticate: Negotiate oRswGaADCgEAoxIEEAEAAADt4oKkY2zs3gAAAAA=
but when I use my machinename in the URI
http://machinename/api/sample/secured
I get these ResponseHeaders
HTTP/1.1 401 Unauthorized
Date: Mon, 30 Nov 2020 17:00:52 GMT
Content-Length: 0
Server: Kestrel
WWW-Authenticate: Negotiate
In a SOAP XML Service Project (with PowerBuilder Clients ) we had used Waffle (https://github.com/Waffle) and PowerBuilder's .NET Proxy approach - but that does not help here :-(
Is anybody using Windows Authentication (Single-Sign-On) with PowerBuilder's RESTClient?
regards
Arnd
