Repository navigation
Conversation
An app whose accounts the identity provider links at sign-in (Okta Cross App Access) has nothing to connect, but the no-fields view still said "Press Connect below to authenticate" under the API's "linked through SSO" notice, and Connect only returned an error. When the API marks the config linkedAtSignIn, the Hub shows the notice alone and drops Connect. Back stays, so the user can return to the list.
…arrowed The fields memo already narrows to a Falcon config, so it carries the flag and the separate type guard goes. The footer builds its buttons as one array instead of pushing onto a mutable one.
…tton The title's back arrow shows under the same conditions as the footer's Back, so an app linked at sign-in can drop the footer actions like the list view does, with no new prop on CardFooter.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
With Okta account linking (XAA), an employee's accounts on some apps are linked by the identity provider when they sign in to StackOne. The Hub has nothing to connect for them (ENG-3220).
Today a member who opens one of those apps sees:
Changes
The API now sends
linkedAtSignIn: trueon those configs (StackOneHQ/unified-cloud-api#9206). With it:Configs without the flag render exactly as before.
Testing
npm run lintandnpm testpass on a cleannpm ci.After release
@stackone/hubbump.Summary by cubic
Shows only the automatic-linking notice for apps whose accounts are linked at sign-in, instead of prompting users to connect and letting them hit a Connect action that errors with a 422.
linkedAtSignInflag on connector configs to hide the "Press Connect below to authenticate" prompt and the footer actions; Back stays so users can return to the list.Written for commit f7ea5fa. Summary will update on new commits.