Troubleshooting

This section provides solutions to common issues you might encounter while integrating and using Securix.app.

Common Issues and Solutions

1. API Key Invalid or Unauthorized Errors

Problem: You receive an error indicating that your API key is invalid or that your request is unauthorized.

Possible Causes:

• Incorrect API key provided.
• Expired or revoked API key.
• Insufficient permissions associated with the API key for the requested operation.
• Network issues preventing communication with Securix.app services.

Solutions:

1. Verify API Key: Double-check that the apiKey provided in your SDK configuration exactly matches the one from your Securix.app dashboard. Ensure there are no leading/trailing spaces or typos.
2. Check Key Status: Log in to your Securix.app dashboard to confirm that your API key is active and has not been revoked or expired.
3. Review Permissions: Ensure the API key has the necessary permissions for the operations you are trying to perform (e.g., authorize, encrypt, decrypt).
4. Network Connectivity: Confirm that your application can reach the Securix.app API endpoints. Check firewall rules, proxy settings, or temporary network outages.

2. SDK Initialization Fails

Problem: The SecurixClient or SecurixCore constructor throws an error or the application crashes during initialization.

Possible Causes:

• Missing required configuration parameters (e.g., apiKey).
• Invalid data types for configuration options.
• Environment variable issues (e.g., process.env.SECURIX_API_KEY is undefined).

Solutions:

1. Required Parameters: Ensure all mandatory configuration options (like apiKey) are provided. Refer to the Configuration Guide for details.
2. Type Mismatch: Verify that the values passed to configuration options match the expected data types (e.g., string for apiKey, boolean for flags).
3. Environment Variables: If using environment variables, confirm they are correctly loaded and accessible in your application's environment. For client-side frameworks like Next.js, remember to prefix client-side environment variables with NEXT_PUBLIC_.

3. Policy Evaluation Returns Unexpected Results

Problem: An authorize call returns false when you expect true, or vice-versa.

Possible Causes:

• Incorrectly defined security policies in your Securix.app dashboard.
• Mismatch between the attributes (user, action, resource, context) sent in the authorize request and the policy conditions.
• Caching issues with policies (if you have local caching enabled).

Solutions:

1. Review Policies: Carefully examine your security policies in the Securix.app dashboard. Ensure they correctly reflect your intended access rules.
2. Inspect Request Payload: Log the user, action, resource, and any context attributes you are sending in the authorize request. Compare these values against your policy definitions.
3. Clear Cache (if applicable): If you are caching policy decisions locally, try clearing the cache to ensure you are using the latest policies.

Getting Further Help

If you've tried the above solutions and are still experiencing issues, please:

• Consult the Securix.app API Reference (coming soon) for detailed information on specific functions.
• Check the Securix.app community forums or Discord for similar issues.
• Contact Securix.app Support with detailed logs and error messages.