Code of Conduct
As we have several service types, we want to reflect these types in the file name. It will allow us to easily determine the purpose of usage.
Default service (general-purpose, application business logic): *Service
Examples: LocalisationService, NavigationTreeService
Resource service (state management): *Resource
Examples: UserInfoResource, ConnectionInfoResource
Bootstrap service (application initiation logic): *Bootstrap
Examples: CustomConnectionMenuBootstrap, SQLEditorBootstrap
-
Administration
- Server configuration
- Create Connection
- Connection Templates Management
- Access Management
-
Authentication methods
-
Local Access Authentication
- Anonymous Access Configuration
- Reverse proxy header authentication
- LDAP
-
Single Sign On
-
SAML
-
OpenID
-
AWS OpenID
-
AWS SAML
-
AWS IAM
-
AWS OpenId via Okta
-
Snowflake SSO
-
Okta OpenId
-
Cognito OpenId
-
JWT authentication
-
Kerberos authentication
-
NTLM
-
Microsoft Entra ID authentication
-
Google authentication
-
Local Access Authentication
- Database authentication methods
- Network configuration settings
- User credentials storage
- Cloud databases configuration
-
Query Manager
-
Drivers Management
-
Features
- Server configuration
-
Domain manager
- Product configuration parameters
- Command line parameters
- Local Preferences
- API
- Deployment options
- Additional setup and management