Deprecate SCV socket-based M3 programs

Action required for SCP on-prem and single tenant (ST) cloud deployments only.

These m3.socket parameters in the scv.properties file must be cleared:

• m3.socket.host=
• m3.socket.port=
• m3.socket.user=
• m3.socket.password=
• m3.socket.company.id=

The m3.ws parameters in the scv.properties file must be maintained.

These parameters must always be maintained:

• m3.ws.base.url=
• m3.ws.user=
• m3.ws.company.id=

Rest APIs support these authentication methods:

1. OAuth authentication (preferred mechanism)
2. Certificate authentication (only if OAuth is not possible)
3. Basic authentication (not preferred)

Additional m3.ws parameters must be maintained based on the selected authentication method:

1. OAuth Authentication:
   • m3.ws.oauth.key=
   • m3.ws.oauth.secret=

   The environment team must configure the tenant and provide the OAuth key and Secret key values.

2. Certificate Authentication:
   • m3.ws.keystore.file=
   • m3.ws.keystore.password=
   Note: You can copy the certificate to {SCP install location}\config folder and put only the name of the file for m3.ws.keystore.file property.
3. Basic Authentication:
   • m3.ws.basic.user=
   • m3.ws.basic.password=

This format can be used when providing the user configuration:

• m3.ws.basic.user={domain}\{user}
• m3.ws.user={user}

Maintaining the scv.properties file for M3 integration is also explained in SCV - M3 Integration Guide using API.pdf.