#auth0

did you install all the composer dependencies?

they’re installed in the current directory, not globally

@pose - We were working on an issue with user login before the new year. I have some additional information to share.

merge-py: I think pose’s AFK for a while

you can reach him at pose@auth0.com if you like

yes I installed it in the folder

does that file exist? /Applications/MAMP/htdocs/vendor/autoload.php

if it does, it might be a permissions issue

no

I am not sure from where to get this file

that should be installed automatically by composer

I will ask my question to the group...

We have a set of users that are having trouble logging in to our application. They are having this issue in IE8 and Chrome. I had them try and navigate to https://app.auth0.com/login to verify they can reach Auth0. They just see a blank gray screen. They do not see the login dialog. Any thoughts?

are they seeing any JS errors or falied requests in dev tools?

merge-py: most likely this is a network or configuration issue

I can post a screenshot of Chrome + Devtools Network trace when accessing https://app.auth0.com/login

yes, that would be helpful

OK

any JS errors under Console would help too

OK -- I don't have those :-(

could request them if helpful

https://www.filepicker.io/api/file/KJ23srM0S6SP... https://www.filepicker.io/api/file/8kFnMydQUWcV...

any errors under Console?

What type of network issue could it be?

I’m not sure yet, I’d need to see what errors are being shown

I can see from that screenshot that there are 3 JS errors in the console :)

merge-py: could you ask that user to try again in incognito mode?

I did have them use Incognito before. Still the same issue.

if you could send over the Console errors, that’d be helpful

I have asked the user to do that.

thanks

Hi

I am sorry

but the autoload.php is not there

even with the php api that is working

installing composer did not create vendor/autoload.php

Fadafido: could you run “find .” in the MAMP directory where you put the seed project?

that will output a list of all the files in the directory and subdirectories

and post the output here, of course :)

hhhh

I found Autoloader.php

but no autoload.php

could you send me the full output?

found it

finally

worked

thanks rolodato

great!

where was it?

in the old folder of the project

Looking for some help on getting linkedin hooked with using the auth0 angular api and custom login.

but not sure why it created there while I run the composer in other folders too

I believe if you install all the composer dependencies it should create the autoload file

ok

hi Patrick213, what issues are you facing?

hope I will not face issues when I upload it to godaddy

let us know if you do, we’ll help you out :)

Hey rolodata, So I've been following the api document and have a button which makes a call to the linked in connection using the popup. Auth0 in the client will show me that the user was able to log in with linked but on the callback in the popup I get a "oops page".

It basically blows up in the popup window and it forces you to close it which causes it to go through the loginFailure route

does this only fail for linkedin, or are you using any other provider?

fails for google too

url https://login.auth0.com/login/callback?code=AQS...

popup shows Oops! Looks like something went wrong!

Auth0 dashboard says that I just logged in using linkedin....

Soooo it almost works :)

In Auth0, connections tab, social, all are checked "on"

Do I have to do something in the "settings", "allowed callback URLs?

have you set an allowed callback URL for your app?

authProvider.init has "callbackURL: location.href"

in the Auth0 dashboard, I mean

Is that where I set that?

I'm guessing the issue is the callback...

you’ll need to add your app’s URL to the list of “allowed callback URLs”

did that

could you PM me your Auth0 domain name?

e.g. example.auth0.com

Do I need to allow "login.auth0.com" as one of them?

no, that’s not necessary

Patrick213: thanks, let me check

Hi, I have a question on the most basic angular auth sample that autogenerated for me

The file auth0-variables defines the "var AUTH0_CALLBACK_URL=location.href;"

At the same time, my registered URL is "http://petcms.congral.org"

what is the relationship between my registered URL and this AUTH0_CALLBACK_URL???

Hi Nik, by registered URL you mean Allowed Callback URL?

Yes, the Allowed Callback URLs from my settings page

location.href is a shorthand to say "the URL where this page is being displayed in the browser"

it's full name is window.location.href

Further, the seed sample's readme says Go to http://localhost:3000 and you'll see the app running :).

if you are displaying/hosting your page at any of the Allowerd Callback URLs it will work transparently

This is not compatible with my Allowed Callback URL

Yes, you need to add <http://localhost:3000>; to your Allowed Callback URLs

It won't work out-of-the-box unfortunately for security reasons

OK, I missed the (obvious) fact that I can have multiple allowed callbacks

It's not obvious at all, we can do a better job at that UX :simple_smile:

So, to be sure: do I leave the var AUTH0_CALLBACK_URL=location.href; as is in the auth0-variables.js file as is, or do I substitute the location.href

with one of the allowed callbacks? (in other words, is the location.href object "known" to angular?

Yes, that object is known to Angular

Darn - that is another place where such explanation would be beneficial :-)

It's basically part of the variables the browser exposes

So, if your question is if there is a more Angular-ish way of doing, I'm not sure

I see - the file auth0-variables.js is completely personalized for my situation,

That's right, and it should be altered to reflect your test configuration, your production configuration, and so on.

Would you care if I get you a document that describes how to run this basic sample in a more angular way with the special focus on running it

Some customers replace that file on compile time with the actual values. So, in your case you can set AUTH0_CALLBACK_URL= "<http://petcms.congral.org>"

on Windows IIS?

Sure, I'd love to see that :smile:

OK Eugenio, I will get you that as well as a lot of other stuff I discussed with "rolodato" earlier. I would like to see a lot more friendly interface

to Windows IIS folks like me

hehe, this is Alberto Pose, :simple_smile: but he's Pace and me Pose, so it's ok

But don't worry, I'll let him know

You may check with Rodrigo as I stated a very strong interest to help auth0 as much as I can

I can vouch for that, and we appreciate it a lot :)

Yes, I'm up to date with that but our system prevented to see the attached images

Sorry for swapping Alberto with Eugenio - I "know" both of you and like auth0 a lot

No problem at all :simple_smile:

Long time ago I had many good discussions with Matthias

So, expect many emails with structured information from me - which I will send to rodrigo's direct email as my screenshots are mangled by your support

email address

nikivancic: actually, that same email was butchered by our tool beforehand :(

the image links are all at the bottom, so it’s hard to understand the email by reading it directly

which is why I sent you the same message to your email address Rodrigo

that’s odd, I saw it the same way in my own inbox (gmail)

Now, let me see if I can make sense from the basic angularjs sample - and then dive some more

I used outlook to write that email, so it must have some special tricks to ensure that all images are displayed at proper locations

Is there any safe way that I can get you my feedback with images at right places? Can you read "markdown" files?

yes, markdown is perfect

sorry we have to waste so much time on such a simple problem :)

Done - thank you both Alberto and Rodrigo for your time

thanks to you Nik :)

Thanks to you Nik, have a great day!

My next email will have a markdown file with suggestion for the basic angularjs sample

It seems that folks from Argentina have terrific attitude

hahah

@rolodato I have a screenshot of the console errors

that’s great!

that’s unusual, let me take a look

merge-py: are your users behind a proxy?

any kind of proxy, really