Security roles: Within the Power Platform and Dynamics 365 Sales, security roles are the standard mechanism to define access levels and permissions for users and service principals to interact with data (like Products).

API key: This is commonly used for "public" or unauthenticated telemetry and usage tracking from external sites. It identifies the application/source without requiring user-level credentials.

Basic authentication: This transmits credentials (username/password) in a header. While it can be used for simple website logins, it is inherently unencrypted (Base64 encoded only) unless wrapped in TLS/SSL.

OAuth: While present in the components, it is not the correct fit for these specific scenarios. OAuth is used for delegated authorization and secure, encrypted token-based access, which contradicts the "no encryption" requirement of the third scenario.

Microsoft Learn - Security roles and privileges: "Security roles define how different users... access different types of records." (Dynamics 365 / Dataverse Documentation).

Microsoft Learn - Use API keys: "An API key is a unique identifier used to authenticate a user, developer, or calling program to an API." (Azure / Power Platform Connector Documentation).

Microsoft Learn - Authentication types for custom connectors: Provides details on Basic authentication (username/password) vs. API Key vs. OAuth 2.0.

IETF RFC 7617: "The 'Basic' HTTP Authentication Scheme" – confirms that the credentials are not encrypted, merely Base64 encoded.

Microsoft Learn - Create or edit a security role: Outlines how roles manage access to entities such as 'Product' within Dynamics 365 Sales.