Future of the plugin

[Morl99]

Hello! I am trying to chime in interested people into a discussion about the Future of this plugin. If you like, please take a look at this PR.

[gbbirkisson]

Hi. The initial author of the plugin here. I think it is time to archive the original repository. I will gladly put a link in the README to the successor of the original plugin. The original repo has 85 forks currently, so I guess it could be up for debate which fork should be considered the successor. Any thoughts on this?

[Morl99]

That is what I was trying to figure out as well. Thanks for chiming in. It looks like we have not yet found anyone that want's to take over. let's wait and see.

[Gruummy]

Hi @Morl99 and @gbbirkisson
i am one of the colleagues which use your plugin in our projekt.
We currently use kong 2.8.3 .. so we had not recognized that here such an issue had beed created.

But now i see it.

The next months we will work on the topic about migration to kong 3.x and when i think about this ... then we also need to port the plugin.

Our project will exist currently longer for ... i think ... a couple of years.
We also have currently no plans to leave kong ... and we use by intention kong OSS ... (Community edition)

Also by intention we made the fork open visible in github. There had been discussions to host it only inhouse ... but this will not happen.

We do not really want to maintain officially a internet repo in our project .. but we will make everything available here.

I think this is the way how opensource should work

[gbbirkisson]

It sounds good to me @ZeeFiix. I will update the README in the original repo pointing to the new repo (https://github.com/telekom-digioss/kong-plugin-jwt-keycloak).

I will also point everyone that has opened issues in the old repo to repoen them in the new repo. I will also do that for PRs.

Once that is done, I will give it a couple of weeks until I archive the repo, just so no issues, PRs are lost.

Sounds good @Morl99 @ZeeFiix ?

[Gruummy]

@gbbirkisson For me yes ...

[Morl99]

Nice, thank you!

[gbbirkisson]

Allright, I have pointed all issues/PRs to move over to this repo. I have also updated the README. I will give it some time before I archive the old repo.

[walter-bd]

Another good fork is this one https://github.com/hanfi/kong-plugin-jwt-keycloak, he adapted the plugin so it works on kong 3.x.x

[Morl99]

I would vote to stay with the telekom fork and merge the changes from hanfi back into that one. Maybe @hanfi is willing to contribute to the new fork as well.

[telekom-digioss]

@Morl99 and @walter-bd
I already have done these .. and other changes meanwhile ... and merged it to master

[gbbirkisson]

Allright, I have pointed all issues/PRs to move over to this repo. I have also updated the README. I will give it some time before I archive the old repo.

I have now archived the old! Thanks for keeping the project alive, and good luck with everything!

[ebarped]

Are you still maintaining this? I see a breaking change in #9 from january, already 4 months old