-
Notifications
You must be signed in to change notification settings - Fork 210
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using for 3rd party tenants #464
Comments
We have a working proof of concept for this, with an API like: server.auth.strategy('twitter', 'bell', {
provider: 'twitter',
password: 'cookie_encryption_password_secure',
clientFunction: async function (request, settings) {
// Set clientId & clientSecret based on request info, e.g.
// settings.clientId = 'aaaaaaaaaaaa'
// settings.clientSecret = 'aaaaaaaAAAAAAAAaaaaaaaa'
}
}) It does require some changes to how & where Technically it's structured so that any of the If we write up tests and documentation covering this use case, will you accept a PR for it, or do you consider this outside the scope of the normal use? |
Is anyone monitoring the issues here? |
Yes. A new group of maintainers has taken over hapi recently, and we're still getting everything up and running. Sorry for any delay. |
Support plan
Context
How can we help?
We would like to allow our users to build out social logins custom to their project. This means that, within each project and for each social provider, there would be a different
clientId
andclientSecret
.Example:
Project A, Twitter login:
clientId: aaaaaaaaaaaaaaaa
clientSecret: aaaaaaaaAAAAAAAAaaaaaaaAAAAAAA
Project B, Twitter login:
clientId: bbbbbbbbbbbbbbbb
clientSecret: bbbbbbbBBBBBBBBBbbbbbbbBBBBBBB
However the documented method is to configure for a single application for each provider and then register a route handler:
Registration
Route handler
Is it possible to perform the Registration step in some other way? Potential solutions might include:
clientId
/clientSecret
another wayclientId
/clientSecret
and change later in route handlerclientId
andclientSecret
with a method in the options object of the registration, based on a project id in the URLclientId
andclientSecret
as a method in theconfig
object of the route config, based on a project id in the URLIf this is supported, we would love a hint at the documentation. If it is not supported, we would love a nudge in the right direction for how we might implement this ourselves.
Thank you!
The text was updated successfully, but these errors were encountered: