Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change documentation link #585

Merged
merged 1 commit into from
Jan 26, 2024
Merged

Change documentation link #585

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion saspy/doc/source/configuration.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -993,7 +993,7 @@ administration work, nothing an end user needs to deal with. However, if your si
the Viya Certificate (a .pem file) must be downloaded and then the contents of that .pem file be appended to the existing
default .pem certificate that your client machine already uses so that the HTTPS connection can Verify the certificate against
theViya deployment. There's some doc in the admin guide about this
(https://go.documentation.sas.com/doc/en/sasadmincdc/v_038/calencryptmotion/n1xdqv1sezyrahn17erzcunxwix9.htm#p1umnmdi53qfjnn17wqb5aqb8ncx)
(https://go.documentation.sas.com/doc/en/sasadmincdc/default/calencryptmotion/n1xdqv1sezyrahn17erzcunxwix9.htm#p1umnmdi53qfjnn17wqb5aqb8ncx)
but again, that's not something an end user needs to read. It does mean that the Viya admin team should be able to get you
the .pem file from Viya for you to save on your client machine. Since appending it to the default .pem file used by
https on your machine is likely something you can't do anyway (some sites have IT set all of this up so you don't have to),
Expand Down
Loading