-
Notifications
You must be signed in to change notification settings - Fork 3
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.
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
Conversation
Documented security constraints of Scheduler Service. There was a big discussion on this limitation with BTP Scheduler Team, CAP Team and expert from XSSEC library on a SAP OSS Ticket. Customers of BTP Scheduler Service should be aware of this limitation, as it is currently not mentioned in the documentation. If you have any questions, Alexandar was working on the SAP OSS Ticket Case 472642/2024 "Calls for Public CAP-API using BTP Scheduler not working" Best regards, Ben
|
Thank you for your valuable content contribution, @bkrencker! So that we can recognize your contribution in the SAP Community, please check your SAP Community user ID (this is a number) in your personal settings page and share it with us in a reply to this comment. Make sure you just include the number in the reply. Your user ID is displayed as follows: Change display name for User ID N where N is your user ID. For example, 53 is the user ID of the user 'qmacro'. Please note that we are currently refactoring our profile and badge system on the SAP Community, and will start assigning badges again when that's complete. |
|
Hi
My User ID is 2161.
Best regards
…________________________________
Von: sap-doc-bot[bot] ***@***.***>
Gesendet: Freitag, 14. Juni 2024 14:06
An: SAP-docs/btp-job-scheduling-service ***@***.***>
Cc: Krencker Benjamin ***@***.***>; Mention ***@***.***>
Betreff: Re: [SAP-docs/btp-job-scheduling-service] Update concepts-26572ad.md (PR #7)
Thank you for your valuable content contribution, @bkrencker<https://github.com/bkrencker>! So that we can recognize your contribution in the SAP Community<https://github.com/SAP-docs/contribution-guidelines/blob/main/docs/recognition.md>, please check your SAP Community user ID (this is a number) in your personal settings page<https://community.sap.com/t5/user/myprofilepage/tab/personal-profile> and share it with us in a reply to this comment. Make sure you just include the number in the reply.
Your user ID is displayed as follows:
Change display name for User ID N
where N is your user ID. For example, 53 is the user ID of the user 'qmacro'<https://community.sap.com/t5/user/viewprofilepage/user-id/53>.
Please note that we are currently refactoring our profile and badge system on the SAP Community, and will start assigning badges again when that's complete.
—
Reply to this email directly, view it on GitHub<#7 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AM6XG5KPEJOQV6ZM35LXBADZHLMC3AVCNFSM6AAAAABJJX5J2OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRXHA4DAMJRGI>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Commiting the change as discussed with @bkrencker
|
Thank you for your valuable contribution, Ben. The change will be available with the next documentation release on SAP Help Portal. |
commit 9f1b374ae3469af9857ec309afeaf15b464c6ce7
Author: REDACTED
Date: Mon Aug 18 11:40:31 2025 +0000
Update from SAP DITA CMS 2025-08-18 11:40:31
Project: dita-all/jjq1673438782153
Project map: c2f780f61c744155b0bd42b6f38fb70c.ditamap
Output: loio4b3e16d4e4d14242bdc2ab48d2aec6be
Language: en-US
Builddable map: 0d59fbec11074faf8cb91d44023c1659.ditamap
commit cb7f84ae09d627a3a25d413bffb729a3be65b0ac
Merge: 9a1fca7 4a35cec
Author: REDACTED
Date: Wed Aug 13 12:47:06 2025 +0300
Merge pull request #7 from UACP/I024085-patch-1
Update REUSE.toml
commit 4a35ceca3d0967f48363e42dccac3f1e915df365
Author: REDACTED
Date: Wed Aug 13 12:46:51 2025 +0300
Update REUSE.toml
commit 9a1fca76842832622e48983da31135919e6f7728
Merge: 19ec2f2 4801d2f
Author: REDACTED
Date: Wed Aug 13 10:57:44 2025 +0300
##################################################
[Remaining squash message was removed before commit...]
Documented security constraints of Scheduler Service.
There was a big discussion on this limitation with BTP Scheduler Team, CAP Team and expert from XSSEC library on a SAP OSS Ticket.
Customers of BTP Scheduler Service should be aware of this limitation, as it is currently not mentioned in the documentation.
If you have any questions, Alexandar was working on the SAP OSS Ticket Case 472642/2024 "Calls for Public CAP-API using BTP Scheduler not working"
Best regards,
Ben