Skip to content

Commit 5fac9ee

Browse files
renejeglinskyrenejeglinsky
committed
typos and minor changes related to profiling
1 parent c0a7a4c commit 5fac9ee

File tree

1 file changed

+34
-35
lines changed

1 file changed

+34
-35
lines changed

‎guides/security/authentication.md‎

Lines changed: 34 additions & 35 deletions
Original file line numberDiff line numberDiff line change
@@ -109,7 +109,7 @@ MockUsersSecurityConfig : Added mock user {"name":"admin","password":"admin",
109109
</div>
110110

111111
**You should not manually configure authentication for endpoints.**
112-
As the mock user authentication is active, all (CAP) andpoints are [authenticated automatically](#model-auth).
112+
As the mock user authentication is active, all (CAP) endpoints are [authenticated automatically](#model-auth).
113113

114114
<div class="impl java">
115115

@@ -153,8 +153,8 @@ returns successfully (HTTP response `200`).
153153
Mock users are deactivated in production profile by default ❗
154154
:::
155155

156-
[Learn more about advanced authentication options](../../java/security#spring-boot){.learn-more .java}
157-
[Learn more about advanced authentication options](../../node.js/authentication#strategies){.learn-more .node}
156+
[Learn more about advanced authentication options in Java](../../java/security#spring-boot){.learn-more}
157+
[Learn more about advanced authentication options in Node.js](../../node.js/authentication#strategies){.learn-more}
158158

159159

160160
### Preconfigured Mock Users { #preconfigured-mock-users }
@@ -164,8 +164,8 @@ The predefined users are added to [custom mock users](#custom-mock-users) define
164164

165165
You can opt out the preconfigured mock users by setting <Config java>`cds.security.mock.defaultUsers = false`</Config>. { .java }
166166

167-
[Learn more about predefined mock users](../../java/security#preconfigured-mock-users){.learn-more .java}
168-
[Learn more about predefined mock users](../../node.js/authentication#mock-users){.learn-more .node}
167+
[Learn more about predefined mock users in Java](../../java/security#preconfigured-mock-users){.learn-more}
168+
[Learn more about predefined mock users in Node.js](../../node.js/authentication#mock-users){.learn-more}
169169

170170

171171
### Customization { #custom-mock-users }
@@ -201,18 +201,20 @@ cds:
201201
"cds": {
202202
"requires": {
203203
"auth": {
204-
"kind": "mocked",
205-
"users": {
206-
"viewer-user": {
207-
"password": "pass",
208-
"tenant": "CrazyCars",
209-
"roles": ["Viewer"],
210-
"attr": { ... }
204+
"[development]": {
205+
"kind": "mocked",
206+
"users": {
207+
"viewer-user": {
208+
"password": "pass",
209+
"tenant": "CrazyCars",
210+
"roles": ["Viewer"],
211+
"attr": { ... }
212+
}
213+
},
214+
"tenants": {
215+
"name" : "CrazyCars",
216+
"features": [ "cruise", "park" ]
211217
}
212-
},
213-
"tenants": {
214-
"name" : "CrazyCars",
215-
"features": [ "cruise", "park" ]
216218
}
217219
}
218220
}
@@ -251,8 +253,8 @@ MockedUserInfoProvider: Resolved MockedUserInfo [id='mock/viewer-user', name='vi
251253
252254
</div>
253255
254-
[Learn more about custom mock users](../../java/security#custom-mock-users){.learn-more .java}
255-
[Learn more about custom mock users](../../node.js/authentication#mocked){.learn-more .node}
256+
[Learn more about custom mock users in Java.](../../java/security#custom-mock-users){.learn-more}
257+
[Learn more about custom mock users in Node.js.](../../node.js/authentication#mocked){.learn-more}
256258
257259
258260
### Automated Testing { #mock-user-testing }
@@ -293,20 +295,15 @@ public class BookServiceOrdersTest {
293295
Integration tests running in production profile should verify that unauthenticated users cannot access any application endpoints❗
294296
:::
295297
296-
[Learn more about testing with authenticated endpoints](../../node.js/cds-test#authenticated-endpoints){.learn-more .java}
297-
[Learn more about testing](../../java/developing-applications/testing#testing-cap-java-applications){.learn-more .node}
298+
[Learn more about testing in Java.](../../java/developing-applications/testing#testing-cap-java-applications){.learn-more .node}
299+
[Learn more about testing with authenticated endpoints in Node.js.](../../node.js/cds-test#authenticated-endpoints){.learn-more}
300+
[Learn more about unit testing in Node.js.](../../node.js/cds-test#testing-with-cds-test){.learn-more}
298301
299302
300-
<div class="impl node">
301-
302-
[Learn more about unit testing](../../node.js/cds-test#testing-with-cds-test){.learn-more}
303-
304-
</div>
305-
306303
307304
## IAS Authentication { #ias-auth }
308305
309-
[SAP Identity Authentication Service (IAS)](https://help.sap.com/docs/cloud-identity-services) is the preferred platform service for identity management providing following features:
306+
[SAP Identity Authentication Service (IAS)](https://help.sap.com/docs/cloud-identity-services) is the preferred platform service for identity management providing the following features:
310307
- best of breed authentication mechanisms (single sign-on, multi-factor enforcement)
311308
- federation of corporate identity providers (multiple user stores)
312309
- cross-landscape user propagation (including on-premise)
@@ -394,7 +391,7 @@ The [binding](../../java/security#bindings) to service instance of type `identit
394391
</div>
395392
396393
The binding provides access to the identity services on behalf of a concrete client.
397-
**CAP applications can have at most one binding to an IAS instance.** Conversely, multiple CAP applications can share the same IAS intstance.
394+
**CAP applications can have at most one binding to an IAS instance.** Conversely, multiple CAP applications can share the same IAS instance.
398395
399396
Service instance and binding offer the following crucial configuration properties:
400397
@@ -823,9 +820,9 @@ Role collections can be assigned to end users.
823820
824821
For convenience, when adding the XSUAA facet, these artifacts are initially derived from the CDS model:
825822
826-
- **XSUAA Scopes**: For every [CAP role](./cap-users#roles) in the CDS model, a dedicated scope is generated with the exact name of the CDS role.
827-
- **XSUAA attributes** For every [CAP attribute](./authorization#user-attrs) in the CDS model, one attribute is generated.
828-
- **XSUAA role templates** For every scope, a dedicated role template with the exact name is generated. The role templates are building blocks for concrete role collections that finally can be assigned to users.
823+
- **XSUAA scopes**: For every [CAP role](./cap-users#roles) in the CDS model, a dedicated scope is generated with the exact name of the CDS role.
824+
- **XSUAA attributes**: For every [CAP attribute](./authorization#user-attrs) in the CDS model, one attribute is generated.
825+
- **XSUAA role templates**: For every scope, a dedicated role template with the exact name is generated. The role templates are building blocks for concrete role collections that finally can be assigned to users.
829826
830827
```json
831828
{
@@ -848,9 +845,9 @@ For convenience, when adding the XSUAA facet, these artifacts are initially deri
848845
]
849846
}
850847
```
851-
[Learn more about XSUAA attributes](https://help.sap.com/docs/btp/sap-business-technology-platform/setting-up-instance-based-authorizations){.learn-more}
852-
[Lean more about XSUAA security descriptor](https://help.sap.com/docs/btp/sap-business-technology-platform/application-security-descriptor-configuration-syntax){.learn-more}
853-
[Learn how to setup mTLS for XSUAA](https://help.sap.com/docs/btp/sap-business-technology-platform/enable-mtls-authentication-to-sap-authorization-and-trust-management-service-for-your-application){.learn-more}
848+
[Learn more about XSUAA attributes.](https://help.sap.com/docs/btp/sap-business-technology-platform/setting-up-instance-based-authorizations){.learn-more}
849+
[Lean more about XSUAA security descriptor.](https://help.sap.com/docs/btp/sap-business-technology-platform/application-security-descriptor-configuration-syntax){.learn-more}
850+
[Learn how to setup mTLS for XSUAA.](https://help.sap.com/docs/btp/sap-business-technology-platform/enable-mtls-authentication-to-sap-authorization-and-trust-management-service-for-your-application){.learn-more}
854851
855852
At runtime, after successful authentication, the scope prefix `$XSAPPNAME`is removed by the CAP integration to match the corresponding CAP role.
856853
@@ -1280,7 +1277,9 @@ With `cds.security.authentication.authenticateMetadataEndpoints: false` you can
12801277
</div>
12811278
12821279
<div class="node">
1280+
12831281
Automatic authentication enforcement can be disabled via feature flag <Config>cds.requires.auth.restrict_all_services: false</Config>, or by using [mocked authentication](#mock-user-auth) explicitly in production.
1282+
12841283
</div>
12851284
12861285
### Overrule Partially { #partially-auth .java }
@@ -1317,7 +1316,7 @@ Be cautious with the configuration of the `HttpSecurity` instance in your custom
13171316
13181317
### Overrule Fully { #fully-auth }
13191318
1320-
In services meshes such as [Istio](https://istio.io/) the authentication is usually fully delegated to a central ingress gateway and the internal communication with the services is protercted by a secure channel:
1319+
In services meshes such as [Istio](https://istio.io/) the authentication is usually fully delegated to a central ingress gateway and the internal communication with the services is protected by a secure channel:
13211320
13221321
![Service Mesh with Ingress Gateway](./assets/ingress-auth.drawio.svg){width="500px"}
13231322

0 commit comments

Comments
 (0)