Skip to content

Add ability to disable authentication adapter #7952

Closed

Description

@dblythy

New Feature / Enhancement Checklist

Current Limitation

Currently, all internal auth adapters are enabled by default, with no option to disable auth adapters that aren't necessary.

Feature / Enhancement Description

Allow

auth : {
 facebook: {
   enabled: false
 }
}

Example Use Case

n/a

Alternatives / Workarounds

n/a

3rd Party References

n/a

Activity

  1. parse-github-assistant commented on Apr 26, 2022

    @parse-github-assistant

    Thanks for opening this issue!

    • 🎉 We are excited about your ideas for improvement!
  2. mtrezza commented on Apr 26, 2022

    @mtrezza
    Member

    Do we need a separate property for this or just disable them if they are not configured in the Parse Server options? Maybe we can make this breaking change in the future and add the option only temporarily, already with a depreciation warning?

  3. dblythy commented on Apr 27, 2022

    @dblythy
    MemberAuthor

    That's what I was thinking. Disabling them if they are not configured would be a breaking change. Many auth adapters however don't require any backend configuration and depend fully on client side. Perhaps we can make a change:

    • For the adapters that require configuration, if they are in the auth payload (e.g auth.facebook) consider them enabled
    • For the adapters that do not require configuration, they require auth.google.enabled to be enabled.

    This still would be a breaking change, however I think it's one worth pushing through.

  4. mtrezza commented on Apr 27, 2022

    @mtrezza
    Member

    If not every adapter requires server configuration then I guess it doesn't work to only enable them if they are configured server side. I think your suggestion makes most sense to introduce an enabled property that is currently true by default (with a deprecation warning), and then we change this in a later version to false by default so one has to manually enable them - for security.

  5. dblythy commented on Apr 27, 2022

    @dblythy
    MemberAuthor

    Sounds good!

  6. mtrezza commented on May 28, 2022

    @mtrezza
    Member

    Closing via #7953

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    type:featureNew feature or improvement of existing feature

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions