Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feat/credentials sync #371

Merged
merged 2 commits into from
Aug 27, 2019
Merged

Feat/credentials sync #371

merged 2 commits into from
Aug 27, 2019

Conversation

hbagdi
Copy link
Member

@hbagdi hbagdi commented Aug 26, 2019

No description provided.

Credential sync for DB mode has now been moved to decK:
- multiple credentials of the same type can be provisioned
- any change to credentials will now be propagated to Kong #230

With this change, all syncing is now done via decK, providing for a
stable sync with least API calls.

There exists one caveat here, any change to password for basic-auth will
not result in a change in Kong because it is not possible to diff
passwords as Kong hashes them in the API response and DB. There will be
a follow up commit to work around this limitation.

For DB-less mode, the parsing becomes simpler but no functional change
should happen.

This change also lays the foundation for secret based credentials in future.
With passwords hashed in Kong, decK can not detect a drift when the
password is changed.
This change syncs the password change to Kong.
Username changes result in re-creation of the credential in Kong and
they are taken care of by decK.

This change has no effect on the DB-less deployments.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant