{"action":"created","issue":{"url":"https://api.github.com/repos/coreos/dex/issues/877","repository_url":"https://api.github.com/repos/coreos/dex","labels_url":"https://api.github.com/repos/coreos/dex/issues/877/labels{/name}","comments_url":"https://api.github.com/repos/coreos/dex/issues/877/comments","events_url":"https://api.github.com/repos/coreos/dex/issues/877/events","html_url":"https://github.com/coreos/dex/pull/877","id":217164882,"number":877,"title":"re-enable deep linking of connectors","user":{"login":"ibloat","id":1326244,"avatar_url":"https://avatars1.githubusercontent.com/u/1326244?v=3","gravatar_id":"","url":"https://api.github.com/users/ibloat","html_url":"https://github.com/ibloat","followers_url":"https://api.github.com/users/ibloat/followers","following_url":"https://api.github.com/users/ibloat/following{/other_user}","gists_url":"https://api.github.com/users/ibloat/gists{/gist_id}","starred_url":"https://api.github.com/users/ibloat/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ibloat/subscriptions","organizations_url":"https://api.github.com/users/ibloat/orgs","repos_url":"https://api.github.com/users/ibloat/repos","events_url":"https://api.github.com/users/ibloat/events{/privacy}","received_events_url":"https://api.github.com/users/ibloat/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2017-03-27T08:00:49Z","updated_at":"2017-03-28T02:54:57Z","closed_at":"2017-03-28T02:54:57Z","pull_request":{"url":"https://api.github.com/repos/coreos/dex/pulls/877","html_url":"https://github.com/coreos/dex/pull/877","diff_url":"https://github.com/coreos/dex/pull/877.diff","patch_url":"https://github.com/coreos/dex/pull/877.patch"},"body":"It was possible to directly link to connectors in v1, continuing authentication directly with the connector indicated by the connector_id parameter.\r\nUnless there was a reason to remove that feature it would be nice to have it back.\r\n\r\nSince the other two redirects had the same comment I c/p it over."},"comment":{"url":"https://api.github.com/repos/coreos/dex/issues/comments/289647753","html_url":"https://github.com/coreos/dex/pull/877#issuecomment-289647753","issue_url":"https://api.github.com/repos/coreos/dex/issues/877","id":289647753,"user":{"login":"ibloat","id":1326244,"avatar_url":"https://avatars1.githubusercontent.com/u/1326244?v=3","gravatar_id":"","url":"https://api.github.com/users/ibloat","html_url":"https://github.com/ibloat","followers_url":"https://api.github.com/users/ibloat/followers","following_url":"https://api.github.com/users/ibloat/following{/other_user}","gists_url":"https://api.github.com/users/ibloat/gists{/gist_id}","starred_url":"https://api.github.com/users/ibloat/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ibloat/subscriptions","organizations_url":"https://api.github.com/users/ibloat/orgs","repos_url":"https://api.github.com/users/ibloat/repos","events_url":"https://api.github.com/users/ibloat/events{/privacy}","received_events_url":"https://api.github.com/users/ibloat/received_events","type":"User","site_admin":false},"created_at":"2017-03-28T02:54:57Z","updated_at":"2017-03-28T02:54:57Z","body":"The goal is to bypass the connector selection page (let the user select the connector within the app, outside dex)\r\nCurrently dex already has two behaviours, showing the selection page if there is more than one connector, otherwise directly redirecting to the sole connector.\r\nAdding the possibility to explicitly specify the provider does not seem to introduce any new flow from the end-user perspective but requires knowledge of connector IDs on part of the client.\r\nRunning multiple dex instances each with a single provider will work fine for our use case as we plan on having only three connectors enabled but maybe a bit cumbersome if one enabled 20 connectors.\r\nIs enabling certain connectors for certain clients a desired/planned feature or how would you go about associating this information with the client?\r\n\r\nWe will go with multiple single-connector dex instances as it seems the most straight-forward, thank you for that suggestion.\r\nBypassing connector selection might be too niche to justify adding that 'feature' back in especially if it wasn't really intended the first time around, closing this PR."}}
{"actor":{"display_login":"ibloat"}}