You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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:
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.The text was updated successfully, but these errors were encountered: