Parse server and Keycloak linking Auth Adapter

ScorprocS · December 4, 2022, 12:49pm

Hello I’ve just migrate to the parse server 5.4.0.
I was surprised when I saw the depreciation of keycloak adapter
“auth.keycloak is deprecated and will be removed in a future version. auth.keycloak.enabled: true”

My question is what is the recommended way to replace it ?
1- Copy the current keycloak adapter, update it and add custom config

2- Write an other adapter to work with OAuth2 flow ?

I’m looking for the right way and not the fastest

dblythy · December 4, 2022, 3:00pm

You just need to add enabled: true to the adapter. We’re not depreciating the adapters, we’re just making it so they have to be implicitly enabled to be called/used.

github.com/parse-community/parse-server

feat: selectively enable / disable default authentication adapters

parse-community:alpha ← dblythy:disable-auth

opened 01:01PM - 26 Apr 22 UTC

dblythy

+59 -4

### New Pull Request Checklist  - [x] I am not disclosing a [vulnerability](https://github.com/parse-community/parse-server/blob/master/SECURITY.md). - [x] I am creating this PR in reference to an [issue](https://github.com/parse-community/parse-server/issues?q=is%3Aissue). ### Issue Description I would say 100% of configurations use none, or a couple of the internal auth adaptors. However, by default, any auth type is enabled. This can lead to Related issue: #7952 ### Approach Adds `enabled ` option to `auth` options. If `enabled ` === `false`, the auth won't be able to be used. ### TODOs before merging  - [ ] Add tests - [ ] Add changes to documentation (guides, repository pages, in-code descriptions) - [ ] Add [security check](https://github.com/parse-community/parse-server/blob/master/CONTRIBUTING.md#security-checks) - [ ] Add new Parse Error codes to Parse JS SDK - [x] A changelog entry is created automatically using the pull request title (do not manually add a changelog entry)

ScorprocS · December 6, 2022, 9:22pm

OK thanks for the answere.