You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment CORS can be configured on any type of Tessera servers so that the APIs can be accessed from a browser. This is not ideal as ServerType such as Peer-to-peer should not be exposed to outside of Tessera p2p network. Hence this configurations should be restricted to ThirdParty server - the only point where external parties can use to connect to Tessera.
There is a use case for /partyinfo GET api to be called from a browser to retrieve the list of peer public keys. This API would be exposed via ThirdParty server/port.
The text was updated successfully, but these errors were encountered:
Two changes
At the moment CORS can be configured on any type of Tessera servers so that the APIs can be accessed from a browser. This is not ideal as ServerType such as Peer-to-peer should not be exposed to outside of Tessera p2p network. Hence this configurations should be restricted to ThirdParty server - the only point where external parties can use to connect to Tessera.
There is a use case for
/partyinfo
GET api to be called from a browser to retrieve the list of peer public keys. This API would be exposed via ThirdParty server/port.The text was updated successfully, but these errors were encountered: