@GerryNelson  Thanks for this article which is essential when dealing with user directories or SCIM unable to provide POSIX attributes. The default format of the UID/GID displayed in the terminal by the identities plugin with text output mode can be misleading because , being a large integer value, it is displayed using scientific notation hiding the full digit value. I recommend switching to fulljson/json output mode in order to correct this behavior and display the untruncated integer value (sometimes up to 10, 12 digits long).  sas-viya --output fulljson identities show-group --id HR --show-advanced filtering out the result with jq might help also :-). ... View more

@LouGalway_sas  Thanks for sharing these important considerations which are, from a european-based perspective  especially relevant since accented letters (à la carte dishes, née Smith maiden name, piña colada cocktail recipe etc.) or diacritics are ubiquitous in non-english languages (German umlaut, French cedille, Spanish tildes, Romanian ă/î  to name only a few: every european written language might use such modified latin letters , some very commonly).  SAS treats differently accented letters whether you run an ASCII/ISO encoding session or a UTF8 session. The following  page explains it all : https://documentation.sas.com/doc/en/pgmsascdc/9.4_3.5/nlsref/p1pca7vwjjwucin178l8qddjn0gi.htmTherefore migrating data sets from ASCII charsets (Latin1, Latin9, WLATIN1 ) in addition to " affect[ing] data migration in terms of table sizes, data truncation, and the retention of indexes", also directly affects plain SAS code  : baseline syntax must be modified to take into account the presence of accented characters in CHAR variables, by removing accents altogether (if such alterations are acceptable) or replacing string functions with their k-counterparts.  This is very challenging indeed ! Perhaps, extending the native toolbox of SAS might help transitioning towards UTF8 :  providing an extended attribute to store in the descriptor portion of the Data Set the binary flag 1/0 (1= at least one CHAR var. with multi-bytes length) , sparing k-functions altogether (generalizing VARCHAR type with V9 engine might help greatly in this regard), providing NLS procs to detect in bulk the need for so-called internationalization (proc WhereIsMyMultiBytesVar data= ...) etc.    ... View more

@Vj_Govindarajan Thanks for your consideration and reformatting efforts : much easier to read now ! 🙂 I fully agree with @Patrick  : a SAS implementation would be a nice addition. ... View more

Hi @thesasuser ,   did you reach out to SAS Tech Support, is there progress? Also, if you need our support, please do provide the information. Please do note that low effort replies will bring you probably around the same or less. ... View more

@ronan Much appreciated! The wait shouldn't be too long, looking to get it out before the end of the year.  ... View more

@BrunoMueller Thank you for this correction ! I usually configure 'text' as default output mode and forces 'json' value specifically when needed. Now thanks to your tip, I'll use 'fulljson' as well :-). With 'fulljson' output, the activation status becomes indeed retrievable using the enabled (true/false) property. 🙂 ... View more

Hi Thomas I'm good, thanks ! and I hope you are doing well too. The official documentation has a "Security Considerations" for the external postgreSQL configuration : https://go.documentation.sas.com/doc/en/sasadmincdc/v_057/itopssr/p05lfgkwib3zxbn1t6nyihexp12n.htm#p1wq8ouke3c6ixn1la636df9oa1u You can also look into the details of the referenced README file $deploy/sas-bases/docs/configure_postgresql.htm, you'll see another README file is referenced : $deploy/sas-bases/docs/configure_network_security_and_encryption_using_sas_security_certificate_framework.htm and explains how to  "incorporate Additional CA Certificates into the SAS Viya Platform Deployment in Full-stack or Front-door TLS Mode". I hope that helps.   PS:  note that if you have access to the Deployment subscription in learn.sas.com, you can find a hands-on in the Viya Deployment course, where we show how to incorporate the PostgreSQL Server certificate in the SAS Viya platform (for a Viya deployment in Open-source Kubernetes). ... View more

Thank you @ronan ! Excellent addition.   In fact what you mentioned, I'd say it likely applies to most SAS Viya deployments, regardless of the platform behind, since, in the end, it is a general storage performance consideration. ... View more

This suggestion has been implemented based on the previous comment by Shalaka and also as of LTS 2024.03, viya-cli and its plugins are provided as a container. Documentation for this update is available here. ... View more

The IOM connection is for the Workspace (compute) server -- bypasses the metadata server. The SAS extension is not metadata-aware (at this point, not sure if that's something we'll pursue).   If you can use IOM that will give you more features than SSH. See the matrix of connection capabilities here.   ... View more

Hi @GerryNelson ,   Thank you for this interesting post full of details. Is there any plan to integrate this new image into a standard k8s deployment part of Viya Manifest (optionnaly) installed alongside Viya microservices ? A single pod deployment would suffice.   The k8s cluster UI manager (Lens, Openshift console) would then provide a http *serverless* shell terminal to run VIYA Cli commands in addition to the ssh/docker/Jumpbox approach.   One step further would be to provide a new (http Restful) plugin for Web Environment Manager with a ssh console running *into* the Viya CLI Pod  under the authenticated user own credentials. Adding some additionnal CLI to the image (kubectl, kustomize, git, jq) would enable to replace the need for an extra SSH/Linux terminal with full security including client/server authentication sequence (cli auth login) automatically performed.   Ronan ... View more

That was simply wonderful! 🙂   Thank you!   - Dr. Abhijeet Safai ... View more

Hi @ronan thank you for pointing out that omission. I have fixed the post.   You are correct, using export and import between two environments would be an alternative approach. It could be useful in some cases, however it might have its own issues around making sure you move all the content and related configuration.   ... View more

Thanks for the update @AlexBeaver  ! ... View more

Excellent post ! Thanks for sharing. I wasn't aware that fs-based shortcuts might be enabled when filesystem access is switched off : it works like an AllowList access very easy to configure. ... View more