Firstly the rest server doesn't use a card store, it has it's own card store
Secondly the rest server discovers a specific business network on a specific fabric, so any card uploaded into the rest server should not have a different connection profile, it doesn't make sense. The only relevance to what is uploaded is either a name and secret, or name/identity however name is only useful for enrollment purposes only.
The quickest way to solve this is to not use a full card. use the profile from the discovery identity and then use the identity from the card. This way any connection profile changes are centralised.
Firstly the rest server doesn't use a card store, it has it's own card store Secondly the rest server discovers a specific business network on a specific fabric, so any card uploaded into the rest server should not have a different connection profile, it doesn't make sense. The only relevance to what is uploaded is either a name and secret, or name/identity however name is only useful for enrollment purposes only.
The quickest way to solve this is to not use a full card. use the profile from the discovery identity and then use the identity from the card. This way any connection profile changes are centralised.