-
Notifications
You must be signed in to change notification settings - Fork 325
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
Credential Provisioning for SFT authentication #3915
Conversation
b9a526c
to
a788194
Compare
a788194
to
ce96a75
Compare
7d3c6b7
to
4fa3338
Compare
e727c70
to
2adf177
Compare
1378326
to
e0e303e
Compare
e0e303e
to
0a70d58
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't look at the transaction stuff because I don't see why the credentials needs to be stored at all.
1c8cf52
to
247da65
Compare
Removed after discussion. |
247da65
to
f74a574
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
…on't exist Partially cherry-picked from #3915
* Backport #4063 And fix couple of warnings caused by previous commits not being cherry-picked. * integration: Fix order of arguments for getTeamFeature * integration: setField and modifyField create selector paths if they don't exist Partially cherry-picked from #3915 --------- Co-authored-by: Leif Battermann <leif.battermann@wire.com>
https://wearezeta.atlassian.net/browse/WPB-227
Checklist
sft_servers_all
is_federating
Z-Client
headermultiSFT
foris_federating
/integration
changelog.d