Skip to content
This repository was archived by the owner on Aug 20, 2024. It is now read-only.

Clearer error message for known-but-unsupported vs. unknown sign-in providers#52

Open
dlenski wants to merge 3 commits into
awslabs:masterfrom
dlenski:unsupported_providers
Open

Clearer error message for known-but-unsupported vs. unknown sign-in providers#52
dlenski wants to merge 3 commits into
awslabs:masterfrom
dlenski:unsupported_providers

Conversation

@dlenski
Copy link
Copy Markdown
Contributor

@dlenski dlenski commented Dec 8, 2021

  • Fix spelling of 'scrape'/'scraping' in source and comments

  • Include unknown sign-in provider type in user-visible message

  • Distinct error message for sign-in providers that are known but not yet supported by pidgin-chime

    From the JavaScript of app.chime.aws, there are providers called 'okta',
    'federate', and 'sso' which we do not yet support.

By submitting this pull request, I confirm that my contribution is made under the terms of the LGPL 2.1.

…et supported by pidgin-chime

From the JavaScript of app.chime.aws, there are providers called 'okta',
'federate', and 'sso' which we do not yet support.
@pkveton
Copy link
Copy Markdown

pkveton commented Feb 14, 2022

folks, is there any plan to start supporting presently unsupported providers (namely looking for federate)? thx

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants