Integrating with Jazz - for a client without oauth support


Jad El-Khoury
 

Hej

Is it possible to connect to Jazz from a client that cannot support oauth (neither 1 nor 2)? The easiest option is to use Basic Authentication. (The Jazz installation itself does not connect to any external Authentication Provider)

 

If so, how should the rootservices document look like?

I am familiar with this document when it contains the 5 URLs that perform the oauth1 hand-shake.

 

How does it look like when configured for Basic Authentication? Or even auth2?

 

(It seems that I have asked this same question earlier, but that’s the cost of not having things documented/standardized 😊)

 

regards

______________________________

Jad El-khoury, PhD

KTH Royal Institute of Technology

School of Industrial Engineering and Management, Mechatronics Division

Brinellvägen 83, SE-100 44 Stockholm, Sweden

Phone: +46(0)8 790 6877 Mobile: +46(0)70 773 93 45

jad@..., www.kth.se

 


Jad El-Khoury
 

Correction: Is it possible to connect Jazz to an OSLC Provider that cannot support oauth (neither 1 nor 2)? The easiest option is to use Basic Authentication. (The Jazz installation itself does not connect to any external Authentication Provider)

 

 

From: oslc-op@... <oslc-op@...> On Behalf Of Jad El-Khoury
Sent: Friday, 24 February 2023 14:56
To: oslc-op@...
Subject: [oslc-op] Integrating with Jazz - for a client without oauth support

 

Hej

Is it possible to connect to Jazz from a client that cannot support oauth (neither 1 nor 2)? The easiest option is to use Basic Authentication. (The Jazz installation itself does not connect to any external Authentication Provider)

 

If so, how should the rootservices document look like?

I am familiar with this document when it contains the 5 URLs that perform the oauth1 hand-shake.

 

How does it look like when configured for Basic Authentication? Or even auth2?

 

(It seems that I have asked this same question earlier, but that’s the cost of not having things documented/standardized 😊)

 

regards

______________________________

Jad El-khoury, PhD

KTH Royal Institute of Technology

School of Industrial Engineering and Management, Mechatronics Division

Brinellvägen 83, SE-100 44 Stockholm, Sweden

Phone: +46(0)8 790 6877 Mobile: +46(0)70 773 93 45

jad@..., www.kth.se

 


Andrii Berezovskyi
 

Hej Jad,

Lyo has sample code that does this: https://github.com/OSLC/lyo-samples/blob/master/bin/test-jazz-samples.sh

Though I only tested successfully EWM with Basic auth and know that ERM sample can’t handle Basic (yet wink wink).

–Andrew.

On 24 Feb 2023, at 14:55, Jad El-Khoury <jad@...> wrote:

Hej
Is it possible to connect to Jazz from a client that cannot support oauth (neither 1 nor 2)? The easiest option is to use Basic Authentication. (The Jazz installation itself does not connect to any external Authentication Provider)
 
If so, how should the rootservices document look like?
I am familiar with this document when it contains the 5 URLs that perform the oauth1 hand-shake. 
 
How does it look like when configured for Basic Authentication? Or even auth2?
 
(It seems that I have asked this same question earlier, but that’s the cost of not having things documented/standardized 😊)
 
regards
______________________________
Jad El-khoury, PhD
KTH Royal Institute of Technology
School of Industrial Engineering and Management, Mechatronics Division
Brinellvägen 83, SE-100 44 Stockholm, Sweden
Phone: +46(0)8 790 6877 Mobile: +46(0)70 773 93 45
 


Michael Rowe
 

You should also look into details of JAS server, it supports multiple other Authentication methods. Take a look at the following post about the Jazz Authorization Server . https://jazz.net/wiki/bin/view/Deployment/AboutJazzAuthorizationServer


Andrii Berezovskyi
 

Oh, did you mean to have Jazz connect to a non-oauth enabled OSLC endpoint? I misunderstood a bit. Let’s hear from the Jazz experts!

–Andrew.

On 24 Feb 2023, at 15:00, Jad El-Khoury <jad@...> wrote:

Correction: Is it possible to connect Jazz to an OSLC Provider that cannot support oauth (neither 1 nor 2)? The easiest option is to use Basic Authentication. (The Jazz installation itself does not connect to any external Authentication Provider)
 
 
From: oslc-op@... <oslc-op@...> On Behalf Of Jad El-Khoury
Sent: Friday, 24 February 2023 14:56
To: oslc-op@...
Subject: [oslc-op] Integrating with Jazz - for a client without oauth support
 
Hej
Is it possible to connect to Jazz from a client that cannot support oauth (neither 1 nor 2)? The easiest option is to use Basic Authentication. (The Jazz installation itself does not connect to any external Authentication Provider)
 
If so, how should the rootservices document look like?
I am familiar with this document when it contains the 5 URLs that perform the oauth1 hand-shake.
 
How does it look like when configured for Basic Authentication? Or even auth2?
 
(It seems that I have asked this same question earlier, but that’s the cost of not having things documented/standardized 😊)
 
regards
______________________________
Jad El-khoury, PhD
KTH Royal Institute of Technology
School of Industrial Engineering and Management, Mechatronics Division
Brinellvägen 83, SE-100 44 Stockholm, Sweden
Phone: +46(0)8 790 6877 Mobile: +46(0)70 773 93 45
 



Jad El-Khoury
 

Thanks Andrii and Michael

 

But yes, Jazz is the client this time. So, I Jazz, I need to setup the friendship to this other application (acting as an OSLC Server).

The application is written in .Net (So all the Lyo-related libraries and code are of no use).

 

Regards

Jad

 

 

From: Andrii Berezovskyi <andriib@...>
Sent: Friday, 24 February 2023 15:03
To: oslc-op@...; Jad El-Khoury <jad@...>
Subject: Re: [oslc-op] Integrating with Jazz - for a client without oauth support

 

Oh, did you mean to have Jazz connect to a non-oauth enabled OSLC endpoint? I misunderstood a bit. Let’s hear from the Jazz experts!

 

–Andrew.



On 24 Feb 2023, at 15:00, Jad El-Khoury <jad@...> wrote:

 

Correction: Is it possible to connect Jazz to an OSLC Provider that cannot support oauth (neither 1 nor 2)? The easiest option is to use Basic Authentication. (The Jazz installation itself does not connect to any external Authentication Provider)

 

 

From: oslc-op@... <oslc-op@...> On Behalf Of Jad El-Khoury
Sent: Friday, 24 February 2023 14:56
To: oslc-op@...
Subject: [oslc-op] Integrating with Jazz - for a client without oauth support

 

Hej

Is it possible to connect to Jazz from a client that cannot support oauth (neither 1 nor 2)? The easiest option is to use Basic Authentication. (The Jazz installation itself does not connect to any external Authentication Provider)

 

If so, how should the rootservices document look like?

I am familiar with this document when it contains the 5 URLs that perform the oauth1 hand-shake.

 

How does it look like when configured for Basic Authentication? Or even auth2?

 

(It seems that I have asked this same question earlier, but that’s the cost of not having things documented/standardized 😊)

 

regards

______________________________

Jad El-khoury, PhD

KTH Royal Institute of Technology

School of Industrial Engineering and Management, Mechatronics Division

Brinellvägen 83, SE-100 44 Stockholm, Sweden

Phone: +46(0)8 790 6877 Mobile: +46(0)70 773 93 45

 

 


Gentry, Edward
 

Hi Jad,

 

Jazz has different options depending on whether the REST calls are incoming or outgoing from the perspective of Jazz.

 

Incoming: e.g. GET a Jazz resource, POST a modified Jazz resource, GET a Jazz service provider catalog, etc

  • Jazz auth : this is very much like Basic Auth just the Jazz way. It is well documented on Jazz.net
  • OAuth 2.0: IF Jazz is configured to use the Jazz Authentication Server (basically a profile of the Liberty server) then you can use OAuth 2.0 to make call on the Jazz server.

 

Outgoing: e.g. Jazz does a  GET of a resource compact rendering, or Jazz does a GET on  local configuration resource, or LDX/LQE does a GET of another TRS resource etc.

  • OAuth 1.0A and absolutely nothing else. This was underscored very strongly several months ago.

 

 

Probably not good news … you might be SOL here … :/

 

Cheers,

 

Ed

 

From: oslc-op@... <oslc-op@...> On Behalf Of Jad El-Khoury via lists.oasis-open-projects.org
Sent: Freitag, 24. Februar 2023 15:41
To: oslc-op@...
Subject: Re: [oslc-op] Integrating with Jazz - for a client without oauth support

 

Thanks Andrii and Michael

 

But yes, Jazz is the client this time. So, I Jazz, I need to setup the friendship to this other application (acting as an OSLC Server).

The application is written in .Net (So all the Lyo-related libraries and code are of no use).

 

Regards

Jad

 

 

From: Andrii Berezovskyi <andriib@...>
Sent: Friday, 24 February 2023 15:03
To: oslc-op@...; Jad El-Khoury <jad@...>
Subject: Re: [oslc-op] Integrating with Jazz - for a client without oauth support

 

Oh, did you mean to have Jazz connect to a non-oauth enabled OSLC endpoint? I misunderstood a bit. Let’s hear from the Jazz experts!

 

–Andrew.

 

On 24 Feb 2023, at 15:00, Jad El-Khoury <jad@...> wrote:

 

Correction: Is it possible to connect Jazz to an OSLC Provider that cannot support oauth (neither 1 nor 2)? The easiest option is to use Basic Authentication. (The Jazz installation itself does not connect to any external Authentication Provider)

 

 

From: oslc-op@... <oslc-op@...> On Behalf Of Jad El-Khoury
Sent: Friday, 24 February 2023 14:56
To: oslc-op@...
Subject: [oslc-op] Integrating with Jazz - for a client without oauth support

 

Hej

Is it possible to connect to Jazz from a client that cannot support oauth (neither 1 nor 2)? The easiest option is to use Basic Authentication. (The Jazz installation itself does not connect to any external Authentication Provider)

 

If so, how should the rootservices document look like?

I am familiar with this document when it contains the 5 URLs that perform the oauth1 hand-shake.

 

How does it look like when configured for Basic Authentication? Or even auth2?

 

(It seems that I have asked this same question earlier, but that’s the cost of not having things documented/standardized 😊)

 

regards

______________________________

Jad El-khoury, PhD

KTH Royal Institute of Technology

School of Industrial Engineering and Management, Mechatronics Division

Brinellvägen 83, SE-100 44 Stockholm, Sweden

Phone: +46(0)8 790 6877 Mobile: +46(0)70 773 93 45

 

 


Jad El-Khoury
 

Thank you very much Ed. I recall very well now that you say it. But I don’t believe this is written anywhere - yet?  hopefully this will be part of the Linking Profile?

 

This gives me the (undesirable) answer for what I was looking for. (the outgoing option).

 

Has it been a Java application, I could have helped because Lyo handles oauth1. Unfortunately, we are dealing with a .Net application. Interesting to see if I can motivate trying to look for an oauth1 library.

 

regards

Jad

 

 

From: Gentry, Edward <e.gentry@...>
Sent: Friday, 24 February 2023 16:20
To: oslc-op@...; Jad El-Khoury <jad@...>
Subject: RE: [oslc-op] Integrating with Jazz - for a client without oauth support

 

Hi Jad,

 

Jazz has different options depending on whether the REST calls are incoming or outgoing from the perspective of Jazz.

 

Incoming: e.g. GET a Jazz resource, POST a modified Jazz resource, GET a Jazz service provider catalog, etc

  • Jazz auth : this is very much like Basic Auth just the Jazz way. It is well documented on Jazz.net
  • OAuth 2.0: IF Jazz is configured to use the Jazz Authentication Server (basically a profile of the Liberty server) then you can use OAuth 2.0 to make call on the Jazz server.

 

Outgoing: e.g. Jazz does a  GET of a resource compact rendering, or Jazz does a GET on  local configuration resource, or LDX/LQE does a GET of another TRS resource etc.

  • OAuth 1.0A and absolutely nothing else. This was underscored very strongly several months ago.

 

 

Probably not good news … you might be SOL here … :/

 

Cheers,

 

Ed

 

From: oslc-op@... <oslc-op@...> On Behalf Of Jad El-Khoury via lists.oasis-open-projects.org
Sent: Freitag, 24. Februar 2023 15:41
To: oslc-op@...
Subject: Re: [oslc-op] Integrating with Jazz - for a client without oauth support

 

Thanks Andrii and Michael

 

But yes, Jazz is the client this time. So, I Jazz, I need to setup the friendship to this other application (acting as an OSLC Server).

The application is written in .Net (So all the Lyo-related libraries and code are of no use).

 

Regards

Jad

 

 

From: Andrii Berezovskyi <andriib@...>
Sent: Friday, 24 February 2023 15:03
To: oslc-op@...; Jad El-Khoury <jad@...>
Subject: Re: [oslc-op] Integrating with Jazz - for a client without oauth support

 

Oh, did you mean to have Jazz connect to a non-oauth enabled OSLC endpoint? I misunderstood a bit. Let’s hear from the Jazz experts!

 

–Andrew.

 

On 24 Feb 2023, at 15:00, Jad El-Khoury <jad@...> wrote:

 

Correction: Is it possible to connect Jazz to an OSLC Provider that cannot support oauth (neither 1 nor 2)? The easiest option is to use Basic Authentication. (The Jazz installation itself does not connect to any external Authentication Provider)

 

 

From: oslc-op@... <oslc-op@...> On Behalf Of Jad El-Khoury
Sent: Friday, 24 February 2023 14:56
To: oslc-op@...
Subject: [oslc-op] Integrating with Jazz - for a client without oauth support

 

Hej

Is it possible to connect to Jazz from a client that cannot support oauth (neither 1 nor 2)? The easiest option is to use Basic Authentication. (The Jazz installation itself does not connect to any external Authentication Provider)

 

If so, how should the rootservices document look like?

I am familiar with this document when it contains the 5 URLs that perform the oauth1 hand-shake.

 

How does it look like when configured for Basic Authentication? Or even auth2?

 

(It seems that I have asked this same question earlier, but that’s the cost of not having things documented/standardized 😊)

 

regards

______________________________

Jad El-khoury, PhD

KTH Royal Institute of Technology

School of Industrial Engineering and Management, Mechatronics Division

Brinellvägen 83, SE-100 44 Stockholm, Sweden

Phone: +46(0)8 790 6877 Mobile: +46(0)70 773 93 45