Files
breadcrumb-the-shire/pages/admin/permissions/create().php

77 lines
2.7 KiB
PHP
Raw Normal View History

2026-02-04 23:31:53 +01:00
<?php
use MintyPHP\Buffer;
use MintyPHP\Http\SessionStoreInterface;
2026-02-04 23:31:53 +01:00
use MintyPHP\Router;
use MintyPHP\Service\Access\PermissionAuthorizationPolicy;
2026-03-05 11:17:42 +01:00
use MintyPHP\Support\Flash;
use MintyPHP\Support\Guard;
2026-02-04 23:31:53 +01:00
$session = app(SessionStoreInterface::class)->all();
2026-02-04 23:31:53 +01:00
Guard::requireLogin();
2026-03-04 15:56:58 +01:00
$request = requestInput();
$returnTarget = requestResolveReturnTarget();
$closeTarget = requestResolveReturnTarget('admin/permissions');
$createTarget = requestPathWithReturnTarget('admin/permissions/create', $returnTarget);
$currentUserId = (int) ($session['user']['id'] ?? 0);
refactor(creates-batch): migrate roles/permissions/tenants-create (step 10) Cluster-7 batch-replay of the departments-create pilot (step 9). All three remaining create actions follow the same shape with minor domain-specific variations. Each migration touches one action and one policy: * roles-create + RoleAuthorizationPolicy::authorizeAdminRolesCreate — policy previously returned bare allow() with no capabilities; now emits ['can_view_page' => true]. Action passes viewAuthFlags: []. * permissions-create + PermissionAuthorizationPolicy::authorizeAdminPermissionsCreate — same pattern as roles-create. * tenants-create + TenantAuthorizationPolicy::authorizeAdminTenantsCreate — policy already emitted can_manage_sso + can_manage_custom_fields; can_view_page is added as the first capability. Action passes viewAuthFlags: ['can_manage_sso', 'can_manage_custom_fields'] and materializes both booleans from the aggregator capabilities. All three policy updates are tautological — every actor that survives the deny() branches in each policy can by definition see the page. View, Create, and EditContext now share a consistent capability shape across all four core master-data domains (departments, roles, permissions, tenants). Three drift decisions reproduced: * notFoundFlashScopeKey is N/A (no model lookup in create flows). * t() consistency: Flash::success('Role created' / 'Permission created' / 'Tenant created') now flow through t(). * Defensive scope consumption: $canManageAllTenants reads $tenantScope['scope'] === 'all' as a resilient hook even where the policy emits no manage-all flag (roles/permissions are global, tenants-create has no filter logic). Inline comments document the intentional non-consumption of $tenantScope['ids']. Two contract-test pattern updates (AuthzAdminMasterDataContractTest + AuthzAdminTenantsContractTest) shift the assertion targets from AuthorizationService::class to actionCreateContext( — semantically equivalent because the aggregator wraps the same authorize call internally. ActionContextCsrfPairingContractTest now covers nine callers (five edits + four creates) and stays green. Helper file core/Support/helpers/action_context.php is 0-diff for the seventh consecutive migration. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-26 15:00:05 +02:00
$context = actionCreateContext([
'abilityKey' => PermissionAuthorizationPolicy::ABILITY_ADMIN_PERMISSIONS_CREATE,
'context' => ['actor_user_id' => $currentUserId],
'viewAuthFlags' => [],
'forbiddenStrategy' => 'deny',
]);
refactor(creates-batch): migrate roles/permissions/tenants-create (step 10) Cluster-7 batch-replay of the departments-create pilot (step 9). All three remaining create actions follow the same shape with minor domain-specific variations. Each migration touches one action and one policy: * roles-create + RoleAuthorizationPolicy::authorizeAdminRolesCreate — policy previously returned bare allow() with no capabilities; now emits ['can_view_page' => true]. Action passes viewAuthFlags: []. * permissions-create + PermissionAuthorizationPolicy::authorizeAdminPermissionsCreate — same pattern as roles-create. * tenants-create + TenantAuthorizationPolicy::authorizeAdminTenantsCreate — policy already emitted can_manage_sso + can_manage_custom_fields; can_view_page is added as the first capability. Action passes viewAuthFlags: ['can_manage_sso', 'can_manage_custom_fields'] and materializes both booleans from the aggregator capabilities. All three policy updates are tautological — every actor that survives the deny() branches in each policy can by definition see the page. View, Create, and EditContext now share a consistent capability shape across all four core master-data domains (departments, roles, permissions, tenants). Three drift decisions reproduced: * notFoundFlashScopeKey is N/A (no model lookup in create flows). * t() consistency: Flash::success('Role created' / 'Permission created' / 'Tenant created') now flow through t(). * Defensive scope consumption: $canManageAllTenants reads $tenantScope['scope'] === 'all' as a resilient hook even where the policy emits no manage-all flag (roles/permissions are global, tenants-create has no filter logic). Inline comments document the intentional non-consumption of $tenantScope['ids']. Two contract-test pattern updates (AuthzAdminMasterDataContractTest + AuthzAdminTenantsContractTest) shift the assertion targets from AuthorizationService::class to actionCreateContext( — semantically equivalent because the aggregator wraps the same authorize call internally. ActionContextCsrfPairingContractTest now covers nine callers (five edits + four creates) and stays green. Helper file core/Support/helpers/action_context.php is 0-diff for the seventh consecutive migration. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-26 15:00:05 +02:00
$capabilities = $context['capabilities'];
$tenantScope = $context['tenantScope'];
$viewAuth = $context['viewAuth'];
// Permissions are global; $tenantScope['ids'] is intentionally not consumed here.
// $canManageAllTenants stays as a resilient hook for future policy extensions.
$canManageAllTenants = $tenantScope['scope'] === 'all';
2026-02-04 23:31:53 +01:00
2026-03-04 15:56:58 +01:00
$errorBag = formErrors();
2026-02-04 23:31:53 +01:00
$errors = [];
$form = [
'key' => '',
'description' => '',
2026-02-11 19:28:12 +01:00
'active' => 1,
'is_system' => 0,
2026-02-04 23:31:53 +01:00
];
if ($request->isMethod('POST') && !actionRequireCsrf($createTarget, $createTarget, 'csrf_expired')) {
return;
}
if ($request->isMethod('POST')) {
$result = app(\MintyPHP\Service\Access\PermissionService::class)->createFromAdmin($request->bodyAll());
2026-02-04 23:31:53 +01:00
$form = $result['form'] ?? $form;
2026-03-04 15:56:58 +01:00
$errorBag->merge($result['errors'] ?? []);
2026-02-04 23:31:53 +01:00
2026-03-04 15:56:58 +01:00
if (($result['ok'] ?? false) && !$errorBag->hasAny()) {
$action = (string) $request->body('action', 'create');
2026-02-04 23:31:53 +01:00
if ($action === 'create_close') {
refactor(creates-batch): migrate roles/permissions/tenants-create (step 10) Cluster-7 batch-replay of the departments-create pilot (step 9). All three remaining create actions follow the same shape with minor domain-specific variations. Each migration touches one action and one policy: * roles-create + RoleAuthorizationPolicy::authorizeAdminRolesCreate — policy previously returned bare allow() with no capabilities; now emits ['can_view_page' => true]. Action passes viewAuthFlags: []. * permissions-create + PermissionAuthorizationPolicy::authorizeAdminPermissionsCreate — same pattern as roles-create. * tenants-create + TenantAuthorizationPolicy::authorizeAdminTenantsCreate — policy already emitted can_manage_sso + can_manage_custom_fields; can_view_page is added as the first capability. Action passes viewAuthFlags: ['can_manage_sso', 'can_manage_custom_fields'] and materializes both booleans from the aggregator capabilities. All three policy updates are tautological — every actor that survives the deny() branches in each policy can by definition see the page. View, Create, and EditContext now share a consistent capability shape across all four core master-data domains (departments, roles, permissions, tenants). Three drift decisions reproduced: * notFoundFlashScopeKey is N/A (no model lookup in create flows). * t() consistency: Flash::success('Role created' / 'Permission created' / 'Tenant created') now flow through t(). * Defensive scope consumption: $canManageAllTenants reads $tenantScope['scope'] === 'all' as a resilient hook even where the policy emits no manage-all flag (roles/permissions are global, tenants-create has no filter logic). Inline comments document the intentional non-consumption of $tenantScope['ids']. Two contract-test pattern updates (AuthzAdminMasterDataContractTest + AuthzAdminTenantsContractTest) shift the assertion targets from AuthorizationService::class to actionCreateContext( — semantically equivalent because the aggregator wraps the same authorize call internally. ActionContextCsrfPairingContractTest now covers nine callers (five edits + four creates) and stays green. Helper file core/Support/helpers/action_context.php is 0-diff for the seventh consecutive migration. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-26 15:00:05 +02:00
Flash::success(t('Permission created'), $closeTarget, 'permission_created');
Router::redirect($closeTarget);
2026-02-04 23:31:53 +01:00
} else {
$id = (int) ($result['id'] ?? 0);
if ($id > 0) {
$target = requestPathWithReturnTarget("admin/permissions/edit/{$id}", $returnTarget);
refactor(creates-batch): migrate roles/permissions/tenants-create (step 10) Cluster-7 batch-replay of the departments-create pilot (step 9). All three remaining create actions follow the same shape with minor domain-specific variations. Each migration touches one action and one policy: * roles-create + RoleAuthorizationPolicy::authorizeAdminRolesCreate — policy previously returned bare allow() with no capabilities; now emits ['can_view_page' => true]. Action passes viewAuthFlags: []. * permissions-create + PermissionAuthorizationPolicy::authorizeAdminPermissionsCreate — same pattern as roles-create. * tenants-create + TenantAuthorizationPolicy::authorizeAdminTenantsCreate — policy already emitted can_manage_sso + can_manage_custom_fields; can_view_page is added as the first capability. Action passes viewAuthFlags: ['can_manage_sso', 'can_manage_custom_fields'] and materializes both booleans from the aggregator capabilities. All three policy updates are tautological — every actor that survives the deny() branches in each policy can by definition see the page. View, Create, and EditContext now share a consistent capability shape across all four core master-data domains (departments, roles, permissions, tenants). Three drift decisions reproduced: * notFoundFlashScopeKey is N/A (no model lookup in create flows). * t() consistency: Flash::success('Role created' / 'Permission created' / 'Tenant created') now flow through t(). * Defensive scope consumption: $canManageAllTenants reads $tenantScope['scope'] === 'all' as a resilient hook even where the policy emits no manage-all flag (roles/permissions are global, tenants-create has no filter logic). Inline comments document the intentional non-consumption of $tenantScope['ids']. Two contract-test pattern updates (AuthzAdminMasterDataContractTest + AuthzAdminTenantsContractTest) shift the assertion targets from AuthorizationService::class to actionCreateContext( — semantically equivalent because the aggregator wraps the same authorize call internally. ActionContextCsrfPairingContractTest now covers nine callers (five edits + four creates) and stays green. Helper file core/Support/helpers/action_context.php is 0-diff for the seventh consecutive migration. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-26 15:00:05 +02:00
Flash::success(t('Permission created'), $target, 'permission_created');
2026-02-04 23:31:53 +01:00
Router::redirect($target);
} else {
refactor(creates-batch): migrate roles/permissions/tenants-create (step 10) Cluster-7 batch-replay of the departments-create pilot (step 9). All three remaining create actions follow the same shape with minor domain-specific variations. Each migration touches one action and one policy: * roles-create + RoleAuthorizationPolicy::authorizeAdminRolesCreate — policy previously returned bare allow() with no capabilities; now emits ['can_view_page' => true]. Action passes viewAuthFlags: []. * permissions-create + PermissionAuthorizationPolicy::authorizeAdminPermissionsCreate — same pattern as roles-create. * tenants-create + TenantAuthorizationPolicy::authorizeAdminTenantsCreate — policy already emitted can_manage_sso + can_manage_custom_fields; can_view_page is added as the first capability. Action passes viewAuthFlags: ['can_manage_sso', 'can_manage_custom_fields'] and materializes both booleans from the aggregator capabilities. All three policy updates are tautological — every actor that survives the deny() branches in each policy can by definition see the page. View, Create, and EditContext now share a consistent capability shape across all four core master-data domains (departments, roles, permissions, tenants). Three drift decisions reproduced: * notFoundFlashScopeKey is N/A (no model lookup in create flows). * t() consistency: Flash::success('Role created' / 'Permission created' / 'Tenant created') now flow through t(). * Defensive scope consumption: $canManageAllTenants reads $tenantScope['scope'] === 'all' as a resilient hook even where the policy emits no manage-all flag (roles/permissions are global, tenants-create has no filter logic). Inline comments document the intentional non-consumption of $tenantScope['ids']. Two contract-test pattern updates (AuthzAdminMasterDataContractTest + AuthzAdminTenantsContractTest) shift the assertion targets from AuthorizationService::class to actionCreateContext( — semantically equivalent because the aggregator wraps the same authorize call internally. ActionContextCsrfPairingContractTest now covers nine callers (five edits + four creates) and stays green. Helper file core/Support/helpers/action_context.php is 0-diff for the seventh consecutive migration. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-26 15:00:05 +02:00
Flash::success(t('Permission created'), $closeTarget, 'permission_created');
Router::redirect($closeTarget);
2026-02-04 23:31:53 +01:00
}
}
}
}
2026-03-04 15:56:58 +01:00
$validationSummaryErrors = $errorBag->toArray();
$errors = $errorBag->toFlatList();
2026-02-04 23:31:53 +01:00
Buffer::set('title', t('Create permission'));
$breadcrumbs = [
['label' => t('Home'), 'path' => 'admin'],
['label' => t('Permissions'), 'path' => 'admin/permissions'],
['label' => t('Create permission')],
];