Skip to content
This repository was archived by the owner on Nov 23, 2021. It is now read-only.

External systems accessing the application #483

Open
sroeger opened this issue Aug 30, 2016 · 2 comments
Open

External systems accessing the application #483

sroeger opened this issue Aug 30, 2016 · 2 comments

Comments

@sroeger
Copy link

sroeger commented Aug 30, 2016

This issue is taken from a TODO in the sample application in UserProfile in order to clean up the code.

This is the interface for the profile of a user interacting with this application. Currently this can only be a {@link io.oasp.gastronomy.restaurant.staffmanagement.dataaccess.api.StaffMemberEntity} however in the future a customer may login and make a reservation, etc.
TODO: Also an external system may access the application via some service. Then there would be no user profile or it would be empty...

@hohwille
Copy link
Member

hohwille commented Dec 5, 2017

IMHO this one has been neglected for far to long. We should find a clear strategy for authentication and suggested solution to deal with web-frontend and also B2B/backend-communication (microservices, etc.). IMHO best practices are already available from projects and we only need to commit to a solution and get it into action to get out of this messy state here.

@hohwille
Copy link
Member

hohwille commented Dec 5, 2017

I will better do a review on MTS regarding this and see if there is much left to do or we could also close this one...

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

No branches or pull requests

2 participants