Future development

[davidpede]

@hajekj Can we get some clarity on how to proceed with active development?

I've contributed to branch v2.0.0 and have been using it in projects for a while now as it supports v2 endpoints and openid config etc. Has been stable for our use cases but prob still needs work.

I saw your comment here #74 (comment) saying your ditching branch v2.0.0 and there are a few open prs now such as #79 and #76 aimed at master branch which duplicate some work already in v2.0.0.

Can you advise what branch you plan to use for v2 of this library so we know which to target for future commits. Or do we need to merge the 2 branches / create new one for v2 etc?

Happy to help as I make lot of use of this lib but need guidance on your plan

[hajekj]

Hello, the initial idea still is to proceed forward with development of v2 branch. I have however paused my own involvement, because I wanted to see where Microsoft takes both Azure AD and their own libraries (especially speaking of v2 endpoint and MSAL).

Right now, it is quite safe to say that v2 endpoint is okay to go, so I would proceed with keeping v1 version of this library to support v1 endpoint, and then having v2 version to support v2 endpoint if that makes sense. Since v2 endpoint is OIDC certified, it should be much easier to get up and running with it.

I am quite sorry I wasn't able to review and merge those incoming pull requests yet, it is on my to-do list still - and I will do my best to get it done during this weekend.

Let's keep this thread open to discuss the future. I would like to invest some more time in order to finish the v2 library and get it into production.

[davidpede]

Ok great so if Branch v2.0.0 is the next version (oauth2-azure v2) then can I suggest:

• Update readme to make it obvious that v2 endpoint support is in Branch v2.0.0
• Update readme to make it obvious all future pr's should target Branch v2.0.0 unless v1 endpoint bug fixes
• Cherry pick suitable commits from master into v2.0.0 or attempt merge (might be to much or unnecessary)
• Get a oauth2-azure v2.0.0-beta1 or oauth2-azure v2.0.0-rc1 released for testing and to increase awareness

Like I said we've been using v2 endpoints with v2.0.0 for 6 months or so with no issues so a beta release shouldn't be to much work. Happy to help with v2 and yes lets keep this thread open to discuss

[hajekj]

I have merged some of the PRs. I want to setup some better test environment, so that I can test all those changes.

[eotin]

Hi @davidpede @hajekj I've referenced the branch v2.0.0.x-dev from packagist and this version 2.0 is well functioning by updating the metadata to "https://login.microsoftonline.com/tenantID/v2.0/.well-known/openid-configuration".

As davidepede mentionned there is some duplicate code from PR as #76 .
How to you want to proceed ? But it could be nice to have a v2.0.0 stable branch that we can use via packagist.

Thanks a lot