• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • RestClient and Integrated Windows Authentication (Single-Sign-On)

Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (3)

Resolved RestClient and Integrated Windows Authentication (Single-Sign-On)

  1. Advice
0
Votes
Undo
  1. Arnd Schmidt
    Arnd Schmidt
  2. PowerBuilder
  3. Monday, 30 November 2020 11:38 AM UTC

Hi all,

does the PowerBuilder RestClient support Integrated Windows Authentication using "WWW-Authenticate: Negotiate" machanism?

Can someone point me to a description or appeon support website that describes in detail which Authentication Methods are supported by the RestClient?

Any further information is welcome!

Arnd

migrating two main PBLs
Datawindow SaveAs Excel without MS Office installe...
Accepted Answer
Mark Lee @Appeon
Mark Lee @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 1 December 2020 07:29 AM UTC
  2. PowerBuilder
  3. # Permalink

Hi Amd，

 

AFAIK,  currently, Httpclient and RestClient don't support Integrated Windows Authentication using the "WWW-Authenticate: Negotiate" mechanism in PowerBuilder.

But they do support OAuth 2.0  Authorization Server. If you need it, you can refer to the links below: https://docs.appeon.com/pb2019r2/application_techniques/ch19s01.html

https://docs.appeon.com/pb2019r2/application_techniques/ch19.html

https://docs.appeon.com/pb2019r2/application_techniques/ch19s01.html#d0e14294

 

Regards,

Comment
Arnd Schmidt
  1. Arnd Schmidt
  2. Tuesday, 1 December 2020 10:00 AM UTC
Thanks for clarification.
  1. Helpful
There are no comments made yet.
Responses (3)
armando herrera @Appeon
armando herrera @Appeon Accepted Answer Pending Moderation
  1. Monday, 30 November 2020 14:26 PM UTC
  2. PowerBuilder
  3. # 1

Hi Arnd,

Here some links about PowerBuilder RestClient 

Example  (using RESTClient) 
RestClient  
SetJWToken 

 

Regards! 

Comment
There are no comments made yet.
Arnd Schmidt
Arnd Schmidt Accepted Answer Pending Moderation
  1. Monday, 30 November 2020 17:38 PM UTC
  2. PowerBuilder
  3. # 2

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

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.