Skip to content

Update concepts-26572ad.md #7

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

Merged
merged 2 commits into from
Jun 17, 2024
Merged

Update concepts-26572ad.md #7

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
59e6d7f
Update concepts-26572ad.md
bkrencker Jun 14, 2024
c2d7c95
Update docs/20---Concepts/concepts-26572ad.md
danachkov Jun 17, 2024
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
12 changes: 12 additions & 0 deletions docs/20---Concepts/concepts-26572ad.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -158,6 +158,18 @@ You can use the service with multitenant applications developed in the context o



</dd>
</dl>

**Security**

</b></dt>
<dd>

You have to bind the Job Scheduling service instance to the application in the same Cloud Foundry space. When the service calls an endpoint, the request always contains the Authorization header (JWT token). To validate this token, make sure that your application is bound to the Job Scheduling service instance.

For more information, see [Binding Service Instances to Applications](https://help.sap.com/docs/btp/sap-business-technology-platform/binding-service-instances-to-applications?version=Cloud).

</dd>
</dl>

Expand Down