Ok - gotcha.

This issue has nothing to do with SimpleAuthentication but it a general concern for OAuth 2.0.

Depending on the OAuth provider (eg. Google, Facebook or 37 Signals) the redirect url might be required to exactly match the value you send to the provider, for the process to work.

Ok - so what does that mean?

When you create an OAuth API Key with your Provider, you usually have to also provide the return_url value. This is the url which the provider will send the user back to, once the user has provided their password.

This value is UNIQUE. This means, you say : return back to www.mysite.com/oauthReturn. Notice how it's hardcoded to www. this means u can't do other subdomains.

So how do you do subdomains then?

EASY :)

you need to create 1x API KEY per subdomain.

So if you have company1.mysite.com, the log into 37signals and create an apikey thingy for that subdomain. Now, for company2.....com .. create another apikey with 37 signals. Rinse, repeat.

If you have 10000000 subdomains, then you're in trouble.

Now, some providers don't care what value you have for the return url. SimpleAuthentication also sends the return url to the provider so if 37 signals doesn't care .. then you only need to create 1 api key. Providers like Google - they are very strict. if the return url SimpleAuthentication sends across to Google doesn't exactly match the value in the API key setup (under console.developers.google.com) then the oauth stuff fails with an ugly error message.

So there you have it.

Depending on your provider, you might need to create 1x API key per subdomain.

Give it a try and report back here, plz.

Support for subdomain #201

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions