Skip to main content

Scopes and Permissions

Mubarokah ID uses OAuth 2.0 scopes to allow users to grant varying levels of access to their account data to client applications. When your application requests authorization, it must specify which scopes it needs. The user will see these requested scopes on the consent screen and can choose to approve or deny them.

Available Scopes

Here are the primary scopes available through Mubarokah ID:

Scope Hierarchy

Scope Permission Matrix

Always request the minimum number of scopes necessary for your application’s functionality. Requesting excessive scopes can lead to lower user consent rates.

Practical Implementation Examples

1. Basic OAuth Flow with view-user Scope

2. Advanced Implementation with detail-user Scope

3. Token Refresh Implementation

detail-user Scope Approval Process

The detail-user scope provides access to sensitive personal information. Due to the sensitive nature of this data, applications requesting this scope must undergo an administrative approval process.

Approval Requirements

1

Application Registration

Your application must first be registered with Mubarokah ID and have basic OAuth integration working with the view-user scope.
2

Documentation Submission

Submit the following documentation:
  • Privacy Policy: Clear statement on how user data will be handled
  • Data Usage Justification: Detailed explanation of why detailed user information is needed
  • Security Measures: Description of data protection measures in your application
  • Compliance Information: Evidence of GDPR, CCPA, or local data protection compliance
3

Technical Review

Your application will undergo a security review including:
  • Code review of OAuth implementation
  • Security audit of data handling procedures
  • Testing of data deletion capabilities
4

Approval Decision

If approved, your application can successfully request the detail-user scope during OAuth flows. If rejected, reasons will be provided with guidance for resubmission.
Important: Even after obtaining the detail-user scope in an access token, your application will receive a 403 Forbidden error when calling /api/user/details unless your client application has received administrative approval.

Approval Process Implementation

Handling user data, especially sensitive information accessible via the detail-user scope, comes with significant responsibilities.

Data Usage Guidelines

Privacy Compliance Implementation

Error Handling Best Practices

This implementation provides production-ready code examples that can be directly used and tested with the Mubarokah ID OAuth system. All endpoints use the correct https://accounts.mubarokah.com/ domain and include proper error handling, security measures, and compliance considerations.