Skip to content

Conversation

@trevorperrin
Copy link
Contributor

The modifications to login.h and connectionstartframe.h allow a user to optionally provide an authentication mechanism other than the default PLAIN mechanism (username and password).

Modifications to login for supplying a custom security mechanism
Modify constructor comment for consistency
Copy link
Member

@EmielBruijntjes EmielBruijntjes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't understand the change, and we need (at least) more in-code documentation to explain to users why they have to pass a username, password, mechanism and response.

* @param response
*/
Login(const char *user, const char *password, const char *mechanism, const char *response)
: _user(user), _password(password), _mechanism(mechanism), _response(response) {}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you add more in-code documentation? I don't understand the use case where it is up to the caller to supply a username, password, mechanism and response. What sort of values is one supposed to pass here?

Login mylogin("my-username", "my-password", "my-special-login-mechanism", "bla bla bla");

Is this permitted?

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.

2 participants