OAuth/ OAuth2 delegated access to metasfresh

[metas-mk]

Type of issue

Feature request

Current behavior

Currently, it's only possible to have access to metasfresh with username/ password. It's not possible to login in another application and receive a delegated access to metasfresh with right credentials.

Expected behavior

Allow users to choose to have their login via 3rd party application.

Additional details added by @cadavre it works like:

1. on front-end we add buttons like „Login with…”
2. button opens popup window or another page of given provider (Facebook, Google…)
3. after success login on providers site (or clicking „Allow”) – provider makes a redirect response to internal authorization endpoint (that would be somewhere on your side – backend needs to decide which user is logging in)

Let's start with GitHub Login first. Later Twitter, G+ and others.

[cadavre]

Things to think about:

1. What about creating new users?
2. Merging with already existing accounts (backend).
3. What shall happen if user clicks "Login with GitHub" but hasn't connected his regular account with GitHub first?

Front-end site:

1. Add "Login with GitHub" button.
2. Settings: add "Connect with GitHub" button.

[damianprzygodzki]

Waiting here for API.

Connecting with GitHub should be added to settings window by the widget, and here we can add something like 'socialButton' widget type, that would be redirecting to a process of authorization.

[teosarca]

Pls describe what API is needed, i.e. what information shall backend provide/store ?

[damianprzygodzki]

@teosarca

• button in settings to connect to github
• whole process of authentication implemented in current one (https://developer.github.com/v3/guides/basics-of-authentication/)

For frontend shouldn't be difference what option user uses to login.

[teosarca]

Ok, have to read it. Thanks.

[teosarca]

backend task: https://github.com/metasfresh/metasfresh-webui-api/issues/37