The default authentication for seldon deploy follows a kubeflow architecture:
This ‘existing_arrikto’ architecture uses an istio envoy filter to run all requests through a check for an auth token, performed by the OIDC AuthService. If no token is available then the user is sent to dex to login and obtain a token.
LDAP, or another external identity provider, can be used as per the existing_arrikto example and in line with the dex documentation.
In order to enforce restrictions, namespaces for Seldon Deploy are labelled as restricted or unrestricted and with the operations that groups can perform on them. See
Deployments by Namespace under the
Product Tour heading.
Particular paths can also be whitelisted - see
Product Tour > Deployment Details View > Requests to Models