You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
are required. You can obtain them [here](https://developer.sas.com/rest-apis/mysas/applications).
50
+
> [!IMPORTANT]
51
+
> Above is a new developer portal that generates keys used with the new APIM proxy for Viya Orders API. If you have keys generated in the [SAS Apigee Developer Portal] (https://api.apiportal.sas.com), they will work until April 20, 2026.
51
52
-[Go](https://golang.org/) 1.25.6 (or later) or [Docker](https://www.docker.com/) is required if you intend to build your own image.
52
53
-[git](https://git-scm.com/) version 2 or later is required if you intend to clone the repository.
53
54
@@ -118,9 +119,11 @@ Take the following steps to start using SAS Viya Orders CLI:
118
119
[SAS Viya Orders API](https://developer.sas.com/rest-apis/mysas), obtain them [here](https://developer.sas.com/rest-apis/mysas/applications) - instructions can be found on the _Authentication_ tab in the same UI [here](https://developer.sas.com/rest-apis/mysas/docs/getting-started/authentication#obtain-client-credentials).
119
120
120
121
1. Save off the `Client ID` and the `Client Secret` values, which will serve as your API credentials.
121
-
> **NOTE:** You only need one of the `Client Secret` values - either will work.
122
+
> [!NOTE]
123
+
> You only need one of the `Client Secret` values - either will work.
122
124
1. Base64 encode each value.
123
-
> **NOTE:** When base64 encoding the credentials, take care not to encode
125
+
> [!NOTE]
126
+
> When base64 encoding the credentials, take care not to encode
124
127
> end-of-line characters into the result. <br/> Here is an example of the
125
128
> correct way to encode from a Linux command prompt:<br/>
126
129
> `echo -n {secret} | base64`<br/><br/> Here is an example of the
@@ -129,10 +132,13 @@ Take the following steps to start using SAS Viya Orders CLI:
129
132
1. Add both credentials to your configuration file, or define them as
130
133
environment variables:
131
134
132
-
- Assign the encoded value of `Client ID` to `clientCredentialsId` (if using environment variables, use
133
-
`CLIENTCREDENTIALSID`).
134
-
- Assign the encoded value of `Client Secret` to `clientCredentialsSecret` (if using environment variables, use
135
-
`CLIENTCREDENTIALSSECRET`).
135
+
- Assign the encoded value of `Client ID` to `apimClientCredentialsId` (if using environment variables, use
136
+
`APIMCLIENTCREDENTIALSID`).
137
+
- Assign the encoded value of `Client Secret` to `apimClientCredentialsSecret` (if using environment variables, use
138
+
`APIMCLIENTCREDENTIALSSECRET`).
139
+
> [!IMPORTANT]
140
+
> If you are using keys generated in the [SAS Apigee Developer Portal] (https://api.apiportal.sas.com), the property names to convey those in are `clientCredentialsId` / `CLIENTCREDENTIALSID` and `clientCredentialsSecret` / `CLIENTCREDENTIALSSECRET`. These keys will cease to work on April 20, 2026.
141
+
136
142
137
143
1. Select CLI options. You can then specify them on the command line, pass them
138
144
in as environment variables, or include them in a configuration file.
@@ -162,8 +168,8 @@ Take the following steps to start using SAS Viya Orders CLI:
162
168
Here is a sample YAML configuration file that contains client credentials:
163
169
164
170
```
165
-
clientCredentialsId: 1a2B3c4D5e6F7h8I9j10K=
166
-
clientCredentialsSecret: 4D5e6F7g8H9i==
171
+
apimClientCredentialsId: 1a2B3c4D5e6F7h8I9j10K=
172
+
apimClientCredentialsSecret: 4D5e6F7g8H9i==
167
173
```
168
174
169
175
### Running
@@ -213,7 +219,7 @@ using SAS Viya Orders CLI:
213
219
2020/10/02 19:16:30 Using config file: /sasstuff/.viya4-orders-cli.yaml
0 commit comments