sso-multitenant
Pricing
Pay per usage
Go to Apify Store

sso-multitenant
Pricing
Pay per usage
Rating
0.0
(0)
Developer
Nishad Manerikar
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
9 days ago
Last modified
Categories
Features
Limited permissionsMulti-tenantServer interface
Share
SSO Multi-tenant Standby Test
A minimal multi-tenant Standby Actor for testing Console SSO (actorStandby.isConsoleAuthEnabled). Open it in a browser without a token, log in with your Apify account, and the page shows the identity the standby controller forwarded for your request.
Setup
- Push and build the Actor (
usesStandbyMode: trueenables Standby). - In the Actor's Standby settings set Tenancy to Multi-tenant. The Actor has no pricing, so it is a free multi-tenant Actor: every caller is routed to the owner's pool.
- Enable Console auth (
isConsoleAuthEnabled). This setting is admin-only.
What to check
Open the standby URL (https://<user>--sso-multitenant-standby.apify.actor) in a browser, without ?token=:
- You get the controller's login page, and
/.actor/loginsends you through Console OAuth. - After the callback,
/loads and shows:userId: your user ID (X-Apify-User-ID), or your organization's when acting as one.basicUserInfo: the decodedx-apify-basic-user-infoheader (user and impersonated user). It is only sent for SSO requests, so it isnullwhen you call with a token.requestId: theX-Actor-Request-IDthe controller minted.cookieSeenByActorandauthorizationSeenByActor: both should be empty, because the controller strips itsapify_standby_authcookie and the token before proxying.runUserId: the account the run lives in. For multi-tenant this is the Actor owner, for every caller.
- The same-origin
fetch('/whoami')on the page should return 200: the session cookie also authenticates subresource requests. - Log in as a second user (another browser profile) and confirm
userIdchanges whilerunUserIdstays the owner, and that both users hit the same run. /.actor/logoutclears the session; the next load shows the login page again.curlwith a token still works and showsbasicUserInfo: null.
Endpoints
GET /: HTML page with the forwarded identity and the fetch probe.GET /whoami: the same identity as JSON.
No dependencies; plain node:http.