Removing ume.admin.addattrs after updating SPNego addon (note 1457499)

[Former Member]

Have succesfuly updated our spnego setup on a development box to the new add-on version attached to SAP note 1457499 .

Now that the User mapping is a little simpler I'm going to going to use mapping mode of 'principal only' with 'logon_id' as the source. This means we no longer need to maintain a custom attribute defined with ume.admin.addattrs (krb5principalname). Now I'm just trying to work out how to clean-up the old spnego config and cleanly remove all the data previously maintained under krb5principalname.

Does anyone know ->

-Where is the data for any custom ume.admin.addattrs attributes is stored (what table/s)?

-If I remove our custom attribute from ume.admin.addattrs in config tool, does that remove the data or just leave it laying about somewhere in the database?

Note - system is dual stack with the UME datasource in the ABAP backend (dataSourceConfiguration_abap.xml)

Thanks

Daniel

Edited: fixed note number

[Former Member]

Ened up logging this with SAP, advice was to just leave the attribute and data as is, it won't cause a problem eventhough it's not being used or maintained (by us) any more.

[Former Member]

Hi Daniel,

you can also run the UME Consistency Check:

[http://help.sap.com/saphelp_nw72/helpdata/en/44/aecb4253217037e10000000a422035/content.htm|http://help.sap.com/saphelp_nw72/helpdata/en/44/aecb4253217037e10000000a422035/content.htm]

Regards,

Martin

[Former Member]

Thanks Martin, I'd found the check tool mentioned in some other threads, it's been very useful cleaning up 'lost' data from custom attribute fields.

Regards

Daniel