Comprehensive management of RADIUS attribute groups including creation, modification, deletion, and querying. Provides full CRUD operations for organizing RADIUS attributes into logical groups for network authentication and authorization.
- Radius Attribute Group
Radius Attribute Group (1.0.9)
The RADIUS Attribute Group Management API provides comprehensive management of RADIUS attribute groups for network authentication and authorization. RADIUS is a networking protocol that provides centralized authentication, authorization, and accounting management. This API enables organizations to create, modify, and delete RADIUS attribute groups that contain standardized network parameters used in wireless and wired network access control.
- Create and manage RADIUS attribute groups: Organize RADIUS attributes into logical groups for easier management
- Assign attributes to groups: Associate specific RADIUS attributes with groups. The complete list of available RADIUS attributes can be retrieved through the API endpoint
/radiusAttributes. - Query available RADIUS attributes: Browse and search through available RADIUS attributes by vendor, data type, and name
- Manage external service assignments: Link attribute groups to external services and systems for distributed authentication
- Content Types: Supports
application/jsonandapplication/vnd.ruckus.v1+json - API Version: v1.0.9
- Data Formats: JSON with HATEOAS links for resource navigation
- Pagination: Standard pagination with configurable page sizes
- Wireless Network Access: Configure RADIUS attributes for Wi-Fi authentication
- VPN Access Control: Manage user access policies through RADIUS attribute groups
- Guest Network Management: Create attribute groups for different user types
All API calls require valid authentication via Bearer token in Authorization header. Include the JWT token in the Authorization: Bearer <token> header.
The API uses standard HTTP status codes with detailed error messages in the response body. All error responses include a requestId for tracking and debugging purposes.
All endpoints may return these common error responses:
- 400 Bad Request: Invalid input data or validation errors
- 401 Unauthorized: Missing or invalid authentication
- 403 Forbidden: Insufficient permissions
- 404 Not Found: Requested resource doesn't exist
- 409 Conflict: Resource conflict (e.g., duplicate names)
- 422 Unprocessable Entity: Business rule violations
- 500 Internal Server Error: Unexpected server errors