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
Copy file name to clipboardExpand all lines: docs/services/devportal.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ Examples of automated access to HPC resources are:
20
20
21
21
An **application** (or "*client application*" or "*client*") is a software created by users that consumes the resources exposed by an API.
22
22
23
-
At CSCS, it requires [OIDC/OAuth2 access tokens](https://datatracker.ietf.org/doc/html/rfc6749#section-1.4) to authenticate againts an [Identity Provider](#identity-provider-idp) (IdP) in order to access the protected resources.
23
+
At CSCS, it requires [OIDC/OAuth2 access tokens](https://datatracker.ietf.org/doc/html/rfc6749#section-1.4) to authenticate against an [Identity Provider](#identity-provider-idp) (IdP) in order to access the protected resources.
24
24
25
25
An application *consumes* API resources by *subscribing* to the API. At CSCS, applications can be subscribed to multiple APIs.
26
26
@@ -30,10 +30,10 @@ An **identity provider** is an entity that authenticates an application and allo
30
30
31
31
### Production Keys
32
32
33
-
Applications must identify againts the CSCS IdP. To do this, users must create the **production keys** (*Consumer ID* - or *Client ID* -, and *Consumer Secret* - or *Client Secret*) that are going to be used to authenticate.
33
+
Applications must identify against the CSCS IdP. To do this, users must create the **production keys** (*Consumer ID* - or *Client ID* -, and *Consumer Secret* - or *Client Secret*) that are going to be used to authenticate.
34
34
35
35
!!!warning
36
-
The pair Consumer Key and Secret represents a personal credential to access CSCS resources, therefore can't be shared and must be stored securelly (i.e.: not exposed in public repositories, forums, documentation, etc)
36
+
The pair Consumer Key and Secret represents a personal credential to access CSCS resources, therefore can't be shared and must be stored securely (i.e.: not exposed in public repositories, forums, documentation, etc)
37
37
38
38
## Getting started
39
39
@@ -113,7 +113,7 @@ To do this, go to the `Production Keys` view of the desired application and clic
113
113
To regenerate the keys, refer back to the [Configuring Production Keys](#configuring-production-keys) section.
114
114
115
115
!!!info
116
-
After reseting the credentials, you will need to reconfigure your software(s) to use the new keys
116
+
After resetting the credentials, you will need to reconfigure your software(s) to use the new keys
117
117
118
118
### Remove your application
119
119
@@ -136,7 +136,7 @@ The information exposed in the overview view is:
136
136
* Documentation of the API (OpenAPI reference, SDK tools, etc)
137
137
* Community information (Public repository, slack channel)
138
138
* Contact information (developers and business)
139
-
*Bussines plans (amount of requests per minute that are allowed in the API subscription)
139
+
*Business plans (amount of requests per minute that are allowed in the API subscription)
140
140
* Applications owned by the user that are subscribed to the API
0 commit comments