BigData / Apache StreamPark Interview questions
How does StreamPark's LDAP login support work alongside its built-in user accounts?
StreamPark's default authentication is its own built-in username/password accounts, managed inside its own database. LDAP login support was added as an additional, optional authentication path rather than a replacement for that default.
When LDAP is configured, StreamPark can authenticate a user against an organization's existing LDAP directory instead of requiring a separate StreamPark-only password. This matters for organizations that already centralize identity in LDAP or Active Directory-backed LDAP and don't want yet another password to manage and rotate for every internal tool.
Regardless of which authentication path a user comes in through, the same downstream model applies once they're logged in: an ADMIN still has to bind the resulting account to a team before it has any visibility into applications or projects, since authentication and team-based authorization remain separate concerns.
More Related questions...
