Hi All,
Please let me know how to remove release option authorisation in ME55 TCODE.
Regards,
Girish
+91 8892055903
Hi All,
Please let me know how to remove release option authorisation in ME55 TCODE.
Regards,
Girish
+91 8892055903
Hi Pavan,
No, there is option to setup the notification for validity expiry for users. I have seen/noticed in my previous projects but unfortunately no idea how was it enabled.
Every company there would be combination of employees and contractors thus there would be case to give the limited validity to contractors initially and keep extending the validity based on their existence.
if the option is enabled, user get to know that before expiring user account (at least from 15 days/1 month) to contact security admin to extend the user account validity.
BR/Suresh
Hi Holger,
Thanks for your answer. My Basis version is 7.02. As i understand BADI_IDENTITY_SU01_CREATE is working for newer Basis versions. What is the name of badi for Basis version 7.02?
Thank you.
Of course, you can
But you have to chnage status of the request:
And now, you can delete the transport for example in transaction: SE10...
Hi Fatih,
as I wrote the BAdIs BADI_IDENTITY_SU01_CREATE or BADI_IDENTITY_UPDATE do not exist in releases 7.02 and less.
In these old releases we do not have a possibility to prefill user attributes (like parameters) for creating.
In older releases you may use the old exits e.g. the Z_USERS_TRANSFER which you have to put as ID into table SSM_CUST and as PATH you need to put your own function module name.
As example for your function module you may use the function module PRGN_EXIT_USERS_TRANSFER but not need to check for the list of roles in your special case.
But, you need to know that these old exists will not have effect after release 7.02 (if you plan an upgrade) and you need to take care with your implementation not to damage our transaction.
Best Regards,
Holger
Hi,
You need to use exit SUSR0001 to add in custom code that will do what you want i.e. it could warn users that their validity is about to expire, their passwords will expire in x days, do both or simply wish them a happy <insert day of week here>
Hi Nishad,
It is possible for all non org values objects . For which object you would like to do it?
Meta
Hi Suresh,
Alex's suggestion is seems correct, there is no standard / configurable option where you can set or activate Alerts for user validity expiry dates however it can be done via custom code or InfoSet query and procedure that will send an e-mail with a list of users expiring in x days.
for this you need to check with your ABAP team to work on such requirements.
Regards,
Satyajit
Thanks Tim. You have pointed me to a direction to do my research.
Thanks!
Can I say that nothing can be done to accomplish this without introducing new products?
Shawn Huang wrote:
Can I say that nothing can be done to accomplish this without introducing new products?
Yes, that is correct - you need a product that has an SNC library and is used for SSO, so that the SAP GUI user is authenticated in same way as the browser user and the session is also encrypted after the user has authenticated.
Thank you, Mynarik...I had similar situation and your advice / steps worked perfectly.
You must however be careful of solutions which "hobble" PFCG and perform direct updates to the AGR* tables. These will be blocked in future via the package interface concept and you cannot rollback to normal PFCG maintenance -> you have to start over without the tool.
? This statement is really not correct Julius, PFCG is still being used, well at least it is for the CSI tooling, I can't tell about other parties. If companies want to decide to no longer use the tooling they can just stop using at and continue in SAP.
I strongly recommend that if you want to use such tools, then you should acquire them via SAP services contracts for partner products and not external bespoke tools. External besproke tools can be SAP partners as well Julius...
No. According to SAP note 1254821: "SAML Sender-Vouches is supported for SAML 1.1 Assertions. There is no support for SAML Sender-Vouches with SAML 2.0 Assertion."
Thanks
Bruno
when we create a user and try to assign the role in BW system – the system is looking for an access to S_USER_AGR with ACTVT = 02. - based on Trace.
however The system should be looking for S_USER_AGR with Actvt = 22.
do we need to apply any SNOTE ?
Regards,
Satyajit
I agree with you.
I am not familiar with CSI as no one I know uses it, but I am yet to see an attempt to tool derived role equivalents which do not directly update AGR_1252 etc themselves and then generate the profiles in batch.
So yes, one should generally be careful in this area and it is best to license the tools via SAP IMO. That gives you some degree of compatibility and sustainability comfort.
Cheers,
Julius
I guess it depends on the risk appetite of the customer. I for one regretted it every time - big pain which luckily makes itself felt quite soon.
At least with derived roles you have the option to divorce them again from the parent role and then try to save them. Or do that intentionally to build them up to a certain level and then divorce them. Still, much too complicated... :-)
Cheers,
Julius
Satyajitsinh Rahevar wrote:
do we need to apply any SNOTE ?
No, not SNOTE. You will need SE16 access to table PRGN_CUST. In the long texts the note numbers are described.
Cheers,
Julius
ps: I removed some completely irrelevant SAP notes. Don't apply those...
Thanks Julius,
I will check this in my system.
Is NW SSO 2.0 licensed separately from NW? We are running BI SAPNetWeaver 7.3 and I am hoping this covers NW SSO licensing? Can anyone shed light on this? Thanks in advance.
dennis
No, NWSSO is licensed separately. Contact your SAP account manager for details. You can also see SAP Online Shop for list prices.