Viya Compute Contexts have an "Identity Type" option, which allows restrictions on who is allowed to use the context.  Batch Contexts can be allowed to run-as under specific identities, and so there should also be the option to restrict user access to the context via an "Identity Type" option...because the run-as user may have more privileges than all users on the system should have access to, and there currently isn't an option to prevent them from using any batch context on the system. ... View more

SAS Viya currently allows an AD UPN to not be the same name as an SPN in scenarios where a user only IWA's into Viya Login via Kerberos, but not in cases where the Kerberos credentials then need to be delegated downstream to SQLSvr/Hadoop/etc via SAS/ACCESS products.  Some of our clients have internal IT naming-requirements for their UPNs which do not match the HTTP/xxxxxxxxx naming requirements for an SPN.    I'd like to request that Viya support the UPN name being different from the SPN, in scenarios where the Kerberos credentials will be delegated downstream.    Many thanks! ... View more