Closed adriatic closed 9 years ago
An obvious question related to the aurelia-auth-sample
: what are the clientId
strings in auth.config.js
file:
configForDevelopment = {
providers: {
google: {
clientId: '239531826023-xxxxx.apps.googleusercontent.com'
},
linkedin: {
clientId: 'yyyyyyy'
},
facebook: {
clientId: 'zzzzzzzzzzz'
}
}
};
I am just presuming that these are the "secret keys" for your own credentials for each of these authentication providers - and then it makes no sense to keep them in that config file??
I must be missing something here :-)
I took my own sources from github (git clone in a temp folder) and provided server side the correct config.development.js, did both client ander server side npm install, and everything seems to work correctly. This is also confirmed by others. So... difficult for me to see what differs in your setup. It' seems it goes wrong already server side from the log you provide.
Regarding the "secret keys". Well... they are not secret, the cryptographic material in the client project (basically clientIDs) is as public as a public key in an RSA key pair, everyone may know these, because you need them to identify the app (as registered by the authentication provider, e.g. google). What is very private, is the material server side (the client_secret), that's why I didn't check in the file config.development.js server side in github, I don't want that my google account gets compromised. Obviously, you need to replace both client and server side, the Ids en secrets with the ones you register at google/facebook/....
I will debug it nevertheless as the problem (as I understood it) has to do with trying to access my picture (which is a part of my google id) and that is something that might be my account specific, so you could not reproduce it
No, I can't reproduce and quite some people are already using the lib.... But, obviously feel free to re-open the issue if debugging on your side leads to something useful. I would try to put some breakpoints server side.
That is exactly what I want to do - and I use Webstorm for that :-).
could you isolate the problem ?
This could be a false alarm, as I did not provide " my own" versions of data in
client/src/authConfig,js
file (the development variant) under the assumption that I do not need to do it in order to get myself authenticated via Google Sign In.Using the same assumption, I also created a copy of
server/config/config.production.js
and named itconfig.development.js
(without changing its content)I run the
gulp watch
from the client folder (assuming that Gulp will start the server side) and got the "normal" Navigation Skeleton app running. Then I clicked on Login button followed by SIgn in With Google.The "cmd console" shows
and chrome console shows:
I did not try to debug anything yet, as I am aiming at a different target at the moment - writing the about plugins for Aurelia-Guides, so I wanted to peek into some details of a plugin (how does the client of a plugin (aurelia-auth-sample) gain access of plugin)