SAP Datasphere, Authorized Consent Expiration, are we joking?

[albertosimeoni]

Hello,

Today I find another mess for consultants that comes from "whats new datasphere" 2023.24:

1) The scheduled tasks are scheduled by users that develop dataflows and graphical views so they are modeling users not administrators by the fact, but they usually work with administrator privileges to dig into performance issues and other stuff.

2) The users that schedules the chains has not visibility of the consent expiration without logging on the systems and go into options!!!

3) The consequences is that if 1 year ago I as consultant schedule a task in customer system, now my consent is expired and I haven't any visibility of which task in which system is not running!!!!!

Is there a way to give consent without expire?

Is there a way to know which system is not running scheduled task because the consent is expired?

and before of this:

Why Do I need to give consent to run a scheduled task in a system??

What is the advantage of this consent process rather than adding burocracy and creating troubles?

Regards

[hannes_keil · Accepted solution]

Hi Alberto,
we have not changed the way how consent works in the wave. We have only added options to see better when consent will expire.

In regards to you questions

Is there a way to give consent without expire?
No.

Is there a way to know which system is not running scheduled task because the consent is expired?
In the same wave we provided an system wide overview for administrators, that shows who's consent will expire in the future and what the affected tasks are. Once consent has expired every failed task will be logged in the task logs.

Why Do I need to give consent to run a scheduled task in a system??
We don't have the classical application server in the cloud, but a multi service approach. The time keeping service needs to be allowed to execute tasks on behalf of a user, in the respective runtime. As the execution in the runtime (e.g. HANA) will be done under that users authorizations and changes logged with his name in the audit log. The alternative is to create a scheduling user and schedule everything under that user, but this would mean there is only one set of authorizations.

What is the advantage of this consent process rather than adding burocracy and creating troubles?
It is more a technical necessity from the BTP services used to build the solution.

Best

Hannes