Technical User Management | Creating technical roles with the 'Internal Technical User Profile' (visible only to providers) does not actually create them.

[SanaSalem01]

Current Behavior

Upon creating technical user type BPDM Sharing Output Consumer under available under Internal technical userprofile (visible only to providers).

Though api return success response but does not display the created user details on the technical user management screen.

This is misleading for customer.

Recording.2025-05-26.111154.mp4

Expected Behavior

Proper fix should be done from backend (If not then ideally FE should hide this type of technical user option and move this ticket to FE repo post discussion)

Steps To Reproduce

• Login to portal
• Navigate to technical user management
• Create technical user using "Internal technical userprofile (visible only to providers)"
• Add all details & data
• Confirm & look for technical user created

[SanaSalem01]

@evegufy

FYI: We did a quick fix on Cofinity-X side by hiding this technical user "Internal technical userprofile (visible only to providers)" option from UI, since its misleading for customers. Howver, ideally proper fix should be done from backend if this type of user is needed on this screen for any user flow?

Thanks

[saadanzari]

@evegufy to look into this.

[evegufy]

IMO this a side effect of the 25.03 feature eclipse-tractusx/sig-release#987, @Phil91 could you please provide your opinion if this is really bug or maybe "just" some unintuitive behaviour?

[Phil91]

I just checked the database on the ev int environment, and didn't find a technical user name 'test 123'. seems like we have a problem with saving the user, will do further investigation today.
/cc @SanaSalem01 @evegufy

[evegufy]

Changing from bug to enhancement because - as mentioned in my earlier comment - this is works as designed. And IMO this issue should be looked at in the first place from a frontend perspective and made more user friendly from a UX perspective in the portal-frontend.

My comment was meant for another issue --> re-adding bug label