Skip to content
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

Support for SSO on a separate domain #196

Open
robbieaverill opened this issue Apr 29, 2020 · 0 comments
Open

Support for SSO on a separate domain #196

robbieaverill opened this issue Apr 29, 2020 · 0 comments

Comments

@robbieaverill
Copy link

Hi team,

I've been told that it's possible for us to have our provisioning and credentials API on one domain while having our SSO endpoint on another domain.

It doesn't look possible to test this setup using Grafton, because:

  • Grafton doesn't have an argument for the SSO domain
  • If I run Grafton on my SSO domain instead of my API domain it doesn't run the SSO test, since the provisioning test fails

Ideally I could do this:

  • grafton test ... --exclude sso http://api.myservice.com/manifold
  • grafton test ... --include sso http://auth.myservice.com/manifold

I also chucked a cheeky feature request in there for the --include argument, can be ignored for this issue, but it is very difficult to isolate specific tests using the --exclude flag, especially when tests are co-dependent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant