Identityserver4.admin: Connect Admin Api to the Admin UI

Created on 30 Jan 2020  路  10Comments  路  Source: skoruba/IdentityServer4.Admin

Currently, the Admin UI is connected to services directly from the controllers.

I am considering using Admin Api from Admin UI.

It will required some rewrite, but it should be cleaner solution.

Feedback is welcome. 馃憤

Thanks

medium task

Most helpful comment

In my opinion Admin and Admin Api projects can be merged.

Connecting Admin to Api will cause unnecessary navigation, auth steps. That will cause unnecessary delay and complexity. Merging two projects into one and execute all the business logic in common services will be more simple.

Api endpoints can serve under a logical route base name like "/Api/*".

All 10 comments

That's great! This allow us to reduce the maintenance effort and will propagate new features across all system. Remember to use HttpClientFactory and Polly for reduce HTTP connection issues.

Can you describe your idea with Polly?

@skoruba count on me when time comes for this rewrite...

Thank you

Would that mean in general, staying with MVC or going down the SPA route? If SPA would be an option, any thoughts on the frontend stack? Maybe it would be nice to bring some love to https://aurelia.io/

IMHO they deserve being used by great projects to showcase their stuff. :)

I have not too much experience with Aurelia, but would love to get my hands dirty if the time comes.

I want to work still with MVC. Thanks

@devployment I have a lot of experience with aurelia, and it is a awesome JS framework, but it is JS. Although since the project is oriented to rest noting stop us to build a different UI stack. Personally I will chose something closed to the .net world like Blazor, but for now MVC is just fine.

I agree with you @danielmeza - thanks for feedback. Maybe I will consider some rewrite but in the future, current solution with MVC is stable. 馃憤馃徏

In my opinion Admin and Admin Api projects can be merged.

Connecting Admin to Api will cause unnecessary navigation, auth steps. That will cause unnecessary delay and complexity. Merging two projects into one and execute all the business logic in common services will be more simple.

Api endpoints can serve under a logical route base name like "/Api/*".

@mehyaa I agree with you. This merge will required bigger rewrite, so I will work on this issue in Q3 of this year - help with this is really welcome. 馃憤

Hey @skoruba!
Do you want to merge the projects or use the Api on AdminUI for the moment?

Was this page helpful?
0 / 5 - 0 ratings

Related issues

weedkiller picture weedkiller  路  4Comments

we4sz picture we4sz  路  4Comments

skoruba picture skoruba  路  4Comments

papyr picture papyr  路  3Comments

imabdul-dev picture imabdul-dev  路  4Comments