Spring Security aspects of an application
Budget: $30 – $250 USD
Business requirements
• Allow a user to register with the application using an oauth2 provider (primary-account) then associate multiple different accounts from the same oauth2 provider (sub-accounts).
• Once the multiple sub-accounts are associated with a single application user, allow the application to access protected resources using the primary-account or any of the sub-accounts without losing the session of the primary-account.
Technical requirements
• Spring boot 2.5.2 or above
• “new” oauth2 Spring stack only
• Front end using Thymeleaf but no expectations that the front end be “pretty” or “polished”. Just enough to provide the security aspects
• The actual oauth2 provider is private but a working example with GitHub will be acceptable.
• Allow a user to register with the application using an oauth2 provider (primary-account) then associate multiple different accounts from the same oauth2 provider (sub-accounts).
• Once the multiple sub-accounts are associated with a single application user, allow the application to access protected resources using the primary-account or any of the sub-accounts without losing the session of the primary-account.
Technical requirements
• Spring boot 2.5.2 or above
• “new” oauth2 Spring stack only
• Front end using Thymeleaf but no expectations that the front end be “pretty” or “polished”. Just enough to provide the security aspects
• The actual oauth2 provider is private but a working example with GitHub will be acceptable.