This repository has been archived by the owner on Jul 19, 2024. It is now read-only.
Error for '/auth/azureactivedirectory' (AWS Elastic Beanstalk) #21
Comments
|
Hey @abezulski , what versions of Ruby are you using locally and on AWS? |
|
Hi @aj-michael, locally I have 2.1.2 with RubyGems 2.2.2 Here is the AWS Elastic Beanstalk breakdown:
|
|
I fixed this issue by adding require 'net/http' to lib/omniauth/strategies/azure_activedirectory.rb |
flojon
added a commit
to flojon/omniauth-azure-activedirectory
that referenced
this issue
May 29, 2017
|
Thanks @flojon, I see that you created pull request but it has not been done yet. Looking forward to get that done, thanks for your input! |
|
I had the exact same problem. Thanks for the fix! This should really be merged... @aj-michael any chance of getting this merged? |
|
Hi @nerdinand, unfortunately I no longer have write access to this repository. You will need to reach out to someone in the @AzureAD organization. |
tomsabin
pushed a commit
to LBHackney-IT/repairs-management
that referenced
this issue
Jul 2, 2018
To set up this up, you are required to create a new "App registration" within the Azure Active Directory service. Keep note of the Application ID, as this will be the Client ID required for the AAD_CLIENT_ID env variable. You will also be required to add the callback URL to the "reply URL" within the app registry properties, e.g. 'http://localhost:3000/auth/azureactivedirectory/callback'. Currently there is an issue with the omniauth-azure-activedirectory gem whereby we need to require the 'net/http' gem in order for the callback to be registered. See the following open issue for more details: AzureAD/omniauth-azure-activedirectory#21
tomsabin
pushed a commit
to LBHackney-IT/repairs-management
that referenced
this issue
Jul 3, 2018
To set up this up, you are required to create a new "App registration" within the Azure Active Directory service. Keep note of the Application ID, as this will be the Client ID required for the AAD_CLIENT_ID env variable. You will also be required to add the callback URL to the "reply URL" within the app registry properties, e.g. 'http://localhost:3000/auth/azureactivedirectory/callback'. Currently there is an issue with the omniauth-azure-activedirectory gem whereby we need to require the 'net/http' gem in order for the callback to be registered. See the following open issue for more details: AzureAD/omniauth-azure-activedirectory#21
tomsabin
pushed a commit
to LBHackney-IT/repairs-management
that referenced
this issue
Jul 6, 2018
To set up this up, you are required to create a new "App registration" within the Azure Active Directory service. Keep note of the Application ID, as this will be the Client ID required for the AAD_CLIENT_ID env variable. You will also be required to add the callback URL to the "reply URL" within the app registry properties, e.g. 'http://localhost:3000/auth/azureactivedirectory/callback'. Currently there is an issue with the omniauth-azure-activedirectory gem whereby we need to require the 'net/http' gem in order for the callback to be registered. See the following open issue for more details: AzureAD/omniauth-azure-activedirectory#21
tomsabin
pushed a commit
to LBHackney-IT/repairs-management
that referenced
this issue
Jul 6, 2018
To set up this up, you are required to create a new "App registration" within the Azure Active Directory service. Keep note of the Application ID, as this will be the Client ID required for the AAD_CLIENT_ID env variable. You will also be required to add the callback URL to the "reply URL" within the app registry properties, e.g. 'http://localhost:3000/auth/azureactivedirectory/callback'. Currently there is an issue with the omniauth-azure-activedirectory gem whereby we need to require the 'net/http' gem in order for the callback to be registered. See the following open issue for more details: AzureAD/omniauth-azure-activedirectory#21
tomsabin
pushed a commit
to LBHackney-IT/repairs-management
that referenced
this issue
Jul 6, 2018
To set up this up, you are required to create a new "App registration" within the Azure Active Directory service. Keep note of the Application ID, as this will be the Client ID required for the AAD_CLIENT_ID env variable. You will also be required to add the callback URL to the "reply URL" within the app registry properties, e.g. 'http://localhost:3000/auth/azureactivedirectory/callback'. Currently there is an issue with the omniauth-azure-activedirectory gem whereby we need to require the 'net/http' gem in order for the callback to be registered. See the following open issue for more details: AzureAD/omniauth-azure-activedirectory#21
tomsabin
pushed a commit
to LBHackney-IT/repairs-management
that referenced
this issue
Jul 6, 2018
To set up this up, you are required to create a new "App registration" within the Azure Active Directory service. Keep note of the Application ID, as this will be the Client ID required for the AAD_CLIENT_ID env variable. You will also be required to add the callback URL to the "reply URL" within the app registry properties, e.g. 'http://localhost:3000/auth/azureactivedirectory/callback'. Currently there is an issue with the omniauth-azure-activedirectory gem whereby we need to require the 'net/http' gem in order for the callback to be registered. See the following open issue for more details: AzureAD/omniauth-azure-activedirectory#21
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have my azure ad up and running, my app works fine on my local machine, but once deployed to AWS EB, I am getting the following error for route '/auth/azureactivedirectory'.
I have checked logs in AWS and getting this one:
Rack app error: #<NameError: uninitialized constant OmniAuth::Strategies::AzureActiveDirectory::Net>Any ideas what is causing this?
The text was updated successfully, but these errors were encountered: