[Openid-specs-ab] Contributing RP libraries to the Connect WG

[Roland Hedberg]

OK, so the division is as follows (very high level):

cryptojwt:
	Implements the JW* family, RFC 7515-7519

oidcmsg:
	Support for dealing with protocol messages (serialising/deserialising).
	Message verification, like correct value types, allowed values and required values.
	Key handling

oidcservice:
	OIDC is a request-response protocol. Each such interaction is defined to be a service.
	This package implements all the basic services defined by OAuth2/OIDC.
	It also provides an implementation of a class called service context which all the 
	services can store/retrieve information from.

	Each service has 3 public methods:
	- get_request_parameters
	- parse_response
	- update_service_context
	
Up to here which HTTP library is used or how cookie handling is done is undefined.
	
oidcrp:
	This package brings it all together and provides programmers with a simple API to be used when
	they want to add OIDC authentication/OAuth2 authorisation to a web service.

These packages are in a hierarchy so:
+ oidcrp depends on all the others.
+ oidcservice depends on oidcmsg and cryptojwt
+ oidcmsg depends on cryptojwt
+ cryptojwt depends on none of the others

> 1 juni 2018 kl. 22:53 skrev Mike Jones <michael.jones at microsoft.com>:
> 
> Good question, George.  Roland, could you share what you think the readme.md contents will be for the four Python projects?
>  
>                                                        -- Mike
>  
> From: George Fletcher <gffletch at aol.com> 
> Sent: Friday, June 1, 2018 1:08 PM
> To: Mike Jones <Michael.Jones at microsoft.com>; openid-specs-ab at lists.openid.net
> Subject: Re: [Openid-specs-ab] Contributing RP libraries to the Connect WG
>  
> This makes more sense to me and I like the break out. Do we have a high level doc as the purpose of each package? I can guess for all but oidcmsg-<lang>. Which makes me wonder if that is the correct name:)
> 
> Thanks,
> George
> 
> On 6/1/18 3:45 PM, Mike Jones via Openid-specs-ab wrote:
> Roland pointed this out to me:
> Since each of these contains more the one package this won�t work.� Each one must be a project which means that what we should use is:
> �
> https://github.com/openid-JWTConnect-Python
> https://github.com/openid-JWTConnect-Java
> https://github.com/openid-JWTConnect-JS
> �
> After asking about what the packages in each project would be, the current set of proposed names are:
> �
> https://github.com/openid-JWTConnect-Python/cryptojwt-python
> https://github.com/openid-JWTConnect-Python/oidcmsg-python
> https://github.com/openid-JWTConnect-Python/oidcservice-python
> https://github.com/openid-JWTConnect-Python/oidcrp-python
> 
> https://github.com/openid-JWTConnect-Java/cryptojwt-java
> https://github.com/openid-JWTConnect-Java/oidcmsg-java
> https://github.com/openid-JWTConnect-Java/oidcservice-java
> https://github.com/openid-JWTConnect-Java/oidcrp-java
> 
> https://github.com/openid-JWTConnect-JS/cryptojwt-js
> https://github.com/openid-JWTConnect-JS/oidcmsg-js
> https://github.com/openid-JWTConnect-JS/oidcservice-js
> https://github.com/openid-JWTConnect-JS/oidcrp-js
> �
> Further comments from the working group are welcome.
> �
> ��������������������������������������������������������������� -- Mike
> �
> From: Mike Jones 
> Sent: Thursday, May 31, 2018 12:26 PM
> To: 'openid-specs-ab at lists.openid.net' <openid-specs-ab at lists.openid.net>
> Cc: Roland Hedberg <roland at catalogix.se>; Luke Camery <lcamery at google.com>; adawes at google.com
> Subject: Contributing RP libraries to the Connect WG
> �
> As many of you know, Google has commissioned the creation of high-quality JWT/OpenID Connect RP libraries in Python, Java, and JavaScript.� Just as the AppAuth libraries were previously contributed to the OpenID Connect working group, Google would like to contribute these to the working group when they are ready.� The Python library has already achieved certification and is ready.
> �
> As board secretary, I�ve been working with them on some of the logistics of this.� The proposed GitHub project names are:
> �
> https://github.com/openid/JWTConnect-Python
> https://github.com/openid/JWTConnect-Java
> https://github.com/openid/JWTConnect-JS
> �
> These are intentionally somewhat parallel to these existing project names:
> �
> https://github.com/openid/AppAuth-Android
> https://github.com/openid/AppAuth-iOS
> https://github.com/openid/AppAuth-JS
> �
> Core maintainers/committers/reviewers would be identified for each library at the time of its contribution.� Roland Hedberg would be in this set for the Python library.
> �
> This note is to inform the working group of this possibility and to solicit feedback from the working group, since these would become a project of the working group.
> �
> ��������������������������������������������������������������� --- Mike
> �
> �
> �
> 
> 
> 
> _______________________________________________
> Openid-specs-ab mailing list
> Openid-specs-ab at lists.openid.net
> http://lists.openid.net/mailman/listinfo/openid-specs-ab
>  

-- Roland
"Education is the path from cocky ignorance to miserable uncertainty.” - Mark Twain