search

LittleKidogo / mula_spender

Some automated forms to aid in our spending
MIT License
3 stars 0 forks source link

Find authentication configuration #127

Closed zacck-zz closed 6 years ago

zacck-zz commented 6 years ago

Expected Behavior

As a developer when authenticating a user I will direct them to the auth routes /auth/:provider and expect them to Sign In to their chosen provider which will call back, Hower at the moment when I direct the user to a link such as this I get the response below 

Error: invalid_request

Missing required parameter: client_id

Learn more

Request Details
client_id=
redirect_uri=http://mula.co.za/auth/google/callback
response_type=code
scope=email profile
That’s all we know.

Upon futher investigation it seems the application is loosing the configuration settings that are set using System.get_env

Actual Behavior

When we redirect someone for auth, the link breaks due to a missing client_id

Acceptance Criteria

The authorization redirect should enable a user to login with their preffered provider

Steps to Reproduce the Problem

  1. visit http://mula.co.za/auth/google

Specifications

zacck-zz commented 6 years ago

Notes

On the application side this is fixed but an end to end solution has not been introduced

TODO

  1. Enable SSL for the Mula API
  2. Add the SSL link for the authorized callback urls for the Google app