Skip to content
This repository was archived by the owner on Dec 13, 2018. It is now read-only.
This repository was archived by the owner on Dec 13, 2018. It is now read-only.

Add/Remove/Configure Authentication Middleware at Runtime #1132

Closed
Closed
Add/Remove/Configure Authentication Middleware at Runtime#1132
Assignees
HaoK
Labels
1 - Readyenhancementneeds design
Milestone
2.0.0-preview1

Description

@windischb
windischb
opened on Feb 21, 2017

Hi!

Is it possible to add and remove AuthenticationMiddleware at Runtime?
I wan't to configure/add/remove OpenIdConnectAuthenticationProviders inside a WebGui.

I was thinking about storing the ProviderOptions in a Database, with the AuthenticationScheme as GUID.

In my special case i wan't to use IdentityServer4 for multiple Customers.
If an new Customer arrives, i will add a new "Provider" to the Database an register it as Middleware in the pipeline. On the other side, i have to unregister the Provider and delete from Database.

Or maybe is it possible to query the Database on every Challenge if the AuthenticationScheme exists??

Any Ideas?
I have the need to add/remove/configure OpenIdConnectAuthentication without recompile or restart the Asp.net Core WebApplication...

Br

Activity

  1. Tratcher commented on Feb 21, 2017

    @Tratcher
    Tratcher
    on Feb 21, 2017
    Member

    Not today, @hoak is building this feature right now: #1113, your feedback would be appreciated.

  2. windischb commented on Feb 21, 2017

    @windischb
    windischb
    on Feb 21, 2017
    Author

    Thanks!

  3. HaoK commented on Feb 21, 2017

    @HaoK
    HaoK
    on Feb 21, 2017
    Member

    I'll add a unit test today to make sure we support adding and removing schemes dynamically works in the new stack

  4. daboul commented on Feb 22, 2017

    @daboul
    daboul
    on Feb 22, 2017

    Hi. I was wondering the exact same thing and just asked about it on SO.

    http://stackoverflow.com/questions/42365743/installing-a-new-middleware-at-runtime-in-asp-net-core

    I'll definitively give it a try when it's out.

    Thanks.

  5. HaoK commented on Feb 22, 2017

    @HaoK
    HaoK
    on Feb 22, 2017
    Member

    See d92d923 for what it currently looks like, basically its just associating a schemeName with a handlerType in a new service.

  6. Eilon
    added this to the 2.0.0 milestone on Feb 23, 2017
  7. Eilon
    added
    1 - Ready
    enhancement
    needs design
    on Feb 23, 2017
  8. Eilon
    assigned
    HaoK
    on Feb 23, 2017

  9. Eilon commented on Feb 23, 2017

    @Eilon
    Eilon
    on Feb 23, 2017
    Contributor

    We need to carefully consider threading scenarios such as:

    1. Reader/writer scenarios to ensure no unusual exceptions get thrown during normal operations
    2. Consistency within a request to ensure that during a request the state doesn't change (could cause very weird side-effects)

  10. HaoK commented on Apr 13, 2017

    @HaoK
    HaoK
    on Apr 13, 2017
    Member

    Tracked via #1179

  11. HaoK
    closed this as completedon Apr 13, 2017

  12. JohnGalt1717 commented on Nov 20, 2018

    @JohnGalt1717
    JohnGalt1717
    on Nov 20, 2018

    Where's this at? Is this now possible? Is there documentation on how to do it? I need to be able to add/remove these via a UI without having to restart our api layer every time.

    Thanks!

  13. Tratcher commented on Nov 20, 2018

    @Tratcher
    Tratcher
    on Nov 20, 2018
    Member

    Here's a sample: https://github.com/aspnet/AspNetCore/tree/5a6b6c90b6e32ecab4975c546228cc63199f168b/src/AuthSamples/samples/DynamicSchemes

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

Metadata

Metadata

Assignees

Labels

1 - Readyenhancementneeds design

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions