- Configuration
Configuring user and application data access
Implementation requirements
Prerequisites
- Sandbox marketplace access or existing marketplace
- Active users:
- Buyer user: ID/Username
buyeruser, Password "Supersecurepassword123!" - Seller user: ID/Username
selleruser, Password "Supersecurepassword123!"
- Buyer user: ID/Username
- Active buyer company: ID
buyercompany - Example ClientIDs:
- Buyer storefront:
"00000000-0000-0000-0000-000000000000" - Admin backoffice:
"11111111-1111-1111-1111-111111111111" - Middleware API:
"222222222-2222-2222-2222-222222222222" - Middleware Secret:
"supersecureclientsecretstring"
- Buyer storefront:
API client configuration
API clients control application access to marketplace data. Best practice: Use separate clients for each application.
Create buyer storefront client
http
json
JavaScript:
javascript
TypeScript:
typescript
C#:
csharp
Create admin backoffice client
http
json
JavaScript:
javascript
TypeScript:
typescript
C#:
csharp
Create middleware API client
http
json
JavaScript:
javascript
TypeScript:
typescript
C#:
csharp
Security profile configuration
Security profiles define granular data access for individual users.
Create buyer profile
http
json
JavaScript:
javascript
TypeScript:
typescript
C#:
csharp
Create seller profile
http
json
JavaScript:
javascript
TypeScript:
typescript
C#:
csharp
Profile assignment implementation
Assign buyer profile
http
json
JavaScript:
javascript
TypeScript:
typescript
C#:
csharp
Assign seller profile
http
json
JavaScript:
javascript
TypeScript:
typescript
C#:
csharp
Authentication implementation
Buyer authentication
http
JavaScript:
javascript
TypeScript:
typescript
C#:
csharp
Seller authentication
http
JavaScript:
javascript
TypeScript:
typescript
C#:
csharp
Client credentials authentication
http
JavaScript:
javascript
TypeScript:
typescript
C#:
csharp
Implementation considerations
This implementation demonstrates one approach to API client and security profile configuration. The platform supports various configurations to meet specific business requirements. Key points:
-
API client management:
- Separate clients per application
- Appropriate access levels
- Security considerations
-
Security profile design:
- Granular role assignment
- User type separation
- Access control hierarchy
-
Authentication patterns:
- User-based authentication
- System authentication
- Token management
Related reading
If you have suggestions for improving this article, let us know!