flask-dance | OAuth dance with style using Flask

First you should create and register different blueprint for github.

github/init.py

This is because the dependencies are conflicting. Installing one by one, you actually end up installing different (conflicting) versions.

Notice:

Since you use Azure AD as the Flask dance provider, we need to use Microsoft Graph to get user's information. The URL should be https://graph.microsoft.com/v1.0/me. So please update the code resp = blueprint.session.get("/user") to resp = blueprint.session.get("/v1.0/me") in method azure_logged_in. Besides, please note that the azure ad user's information has different names. We also need to update the code about creating users.

For example

Your environment does not have access to an installation of wheel. You should be able to resolve this by adding the line:

RUN pip install wheel

to your dockerfile before you attempt to install your requirements file.

Edit: I missed that virtual environments were being utilized here. I would argue that using a virtual environment is unnecessary in this case unless the OP is using their docker instance to run multiple python applications in parallel. There are cases to be made for using this pattern, though that does not appear to be the case here. As such, my suggestion would be to do away with venv altogether and simply install all dependencies inside the docker instance python installation, which would convert every venv/bin/pip call to a simple pip call.

Based on the comments, the issue was that the EB uses Python 3.7.6, while the OP's dependencies required version 3.7.0.

The solution was to change the dependency to Python 3.7.6.

The current python version running on EB can be found here:

64bit Amazon Linux 2 v3.0.1 running Python 3.7 - Python 3.7.6

Make sure you specify installing that module in Dockerfile:

E.g.

I registered in my Google Console the domain in the authorized URIs

The full redirect URL should be registered for the OAUTH client application in Google Console.

When I try to login, it says that I am redirecting from 127.0.0.1:9852

Your given server configuration has your application served with gunicorn and Apache configured as a proxy server.

In some way the request isn't passed onto gunicorn server with enough information for werkzeug to determine the right hostname.

I suggest employing ProxyPreserveHost directive in your VirtualHost to enable the incoming host to be passed on to gunicorn.