Skip to content

What should the security configuration look like? #7

@peholmst

Description

@peholmst

The current security configuration should be improved:

  • The application services are quite fine-grained, but the views are secured with roles. Because of this, the authorities are roles even though they should be more like permissions.
  • Users need to get assigned lots of roles to be able to do basic tasks.
  • The user database is really simple, but still uses its own custom UserDetailsService. It could just use the built-in Spring Security services if it wasn't for the displayName attribute.
  • There is no way of managing users or changing the password.
  • There is no support for multi-factor authentication.
  • There is no support for passkeys.
  • Having the login UI implemented with Vaadin creates a new session with a Vaadin UI just to be able to login. This can in theory be used as a DoS attack vector. Just hit the login page enough times to consume lots of memory.

Given that this application should demonstrate a proper way of doing security in production, this is just not good enough. But what should we implement instead?

Metadata

Metadata

Assignees

No one assigned

    Labels

    discussionDiscuss alternative solutions or designsenhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions