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

Support passing authentication as part of URI #36

Merged
merged 2 commits into from
May 30, 2018
Merged

Conversation

clue
Copy link
Owner

@clue clue commented May 29, 2018

Quassel supports password-based authentication. If you want to create a "normal"
client connection, you're recommended to pass the authentication details as part
of the URI. You can pass the password h@llo URL-encoded (percent-encoded)
as part of the URI like this:

$factory->createClient('quassel://user:h%40llo@localhost')->then(
    function (Client $client) {
        // client sucessfully connected and authenticated
        $client->on('data', function ($data) {
            // next message to follow would be "SessionInit"
        });
    }
);

Note that if you do not pass the authentication details as part of the URI, then
this method will resolve with a "bare" Client right after connecting without
sending any application messages. This can be useful if you need full control
over the message flow, see the documentation for more details.

@clue clue added this to the v0.7.0 milestone May 29, 2018
@clue
Copy link
Owner Author

clue commented May 30, 2018

Rebased on master now that #37 fixed the risky unit tests that caused PHPUnit to skip tests depending on this and thus leaving the Quassel core "unconfigured" during functional integration tests.

@clue clue merged commit 72f7d44 into clue:master May 30, 2018
@clue clue deleted the login branch May 30, 2018 06:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant