Portal: We should add a text indicating the connection string and key type/value should be presented in a fixed order (Primary, Secondary)

[zhenlan]

We should have "Connection String" in front of the connection string box.

In addition, in the screenshot above, the "Secondary" comes before the "Primary", which sounds like another bug.

[zhenlan]

Alternatively, we can have "Primary Connection String", "Secondary Connection String" etc.

[mlacouture]

it seems the issue with the secondary key before the primary key is fixed, I can't reproduce it.

[mlacouture]

The subtitles "Primary", "Secondary", and corresponding RO values come from the server ...

[mlacouture]

The key name order follows the order keys are recreated, it should be a fixed order. And the string that comes from the server needs to be translated into one provided by the portal (localizable and containing the connection string words).

[zhenlan]

The service (RP) won't guarantee the order of keys and the portal should not depend on it.
The service (RP) won't have localized strings. The portal should own the resource strings.

Therefore, the portal should

• Check the Primary or Secondary (in addition to the read-only field) and order the keys properly
• Write label for each output box (eg. "Primary", "Secondary" and "Connection string"). This will be localized by the portal.

[mlacouture]

Fixed committed.