samlsinglesignon extension typecode clash with custom itemtype deployment (Hybris 6.7)

[agrabovskis]

Hybris 6.7 in samlsinglesignon extension introduced new typecodes ('10100' and '10101') that conflict with our custom typecodes. According to documentation (https://help.hybris.com/6.7.0/hcd/8c6254f086691014b095a08a61d1efed.html), the 10000+ typecodes (with few exceptions) should be fine for selection.

Dear SAP:

1. is the documentation outdated or is that a bug?

2. how can we work around the typecode clash issue?

[agrabovskis · Accepted solution]

Sebastian, the latest thing that I know is that on September 2018 there was an official case raised in Jira (https://jira.hybris.com/browse/ECP-3217) but it was marked resolved by stating that it is not going to be fixed.

It's a shame, that SAP fails to ensure these guarantees, because that impacts the trust in their statements (and Hybris is not teenager-built PHP framework where you can expect promises to be broken).

That said I see these options:

• Copy&paste the samlsinglesignon-items.xml to "customize" folder, change the type code and maintain it on your own. This is bad since you might miss the updates in items.xml

• Change the type code of your custom item type (the supported scenario is 11-step process, but more hacky approach is updating ydeployments table and updating PK to match the new value)

Feel free to add more alternatives if I have missed something.

[sebauer]

Any updates on that? We are facing the same problem.

[agrabovskis]

Sebastian, I had to answer my own question with updated findings that had during chat with my colleagues. Please see the answer below. Also I will have to accept my answer, since there is no better answer candidate.