- Identity and Access Management
- Book
- MidPoint
- Developer Zone
- Design Notes
- (Idea of) Communication with Remote Workflow Management System
- Access Certification - requirements draft
- AD Connector Design Notes
- AI Thoughts
- apply-schemas-and-security-4.8
- Approvals terminology
- Archetypes Design Notes
- Assignment Evaluator Questions and Ideas
- Bulk actions (unordered notes)
- Changes in Resource-Related Definitions in 4.5
- Compliance
- Concepts in approvals, certification, and remediation
- Concurrency and Thread Safety
- Configuring individual task handlers
- Content assistant of Axiom Query language
- Dashboards, Widgets and Reports Design Notes
- Deltas in Projector and Clockwork
- deployment-methodology
- Design Meeting
- DOT renderer troubleshooting
- Efficient Deployment Ideas
- Entitlement Design Notes
- Error handling and task suspension in LiveSync
- Grouper Integration Notes
- GUI Profile & Cache Invalidation Updates for 4.6
- How to display approval case (planned or real) execution
- How to use workflows in a self-service scenario
- Identifier Theory
- Incomplete Items (state in 4.9.1)
- Item Path Canonicalization Examples
- Iterative search in midPoint 3.9 and later
- Lifecycle
- Lightweight asynchronous tasks
- Mapping Notes
- MidPoint 5 Vision
- MidPoint Deployment Language Draft
- Midpoint Query: Next Evolution
- Midpoint Studio switch to Gradle
- Multi-node, partitioned and stateful tasks
- New approvals - sample data structures
- Object Names and Labels
- Obtaining results of asynchronous bulk actions
- On Asynchronous Processing
- On Multiple Node Reconciliation
- Parallel and Asynchronous Provisioning
- Password Caching in 4.9.1
- Performance Improvements in 4.8
- Policy Constraints
- PolyString Design Notes
- Profiling Concepts
- Projector and clockwork internals
- Provisioning Scripts vs Postponed Operations
- Query API: Proposed Features for 4.6
- Relation Repository
- Repository query interpreter (Query API → HQL)
- Resource Schema Improvements in 4.6
- Role Mining Design Notes
- Schema cleanup in 4.8
- Schema migration and raw values
- SchemaDoc NG Design Notes
- SCIM Troubles
- Scripting (bulk actions) variables
- Security Improvements in 4.8
- Shadow Metadata and Auditing
- shadow-caching-4.9
- Shibboleth integration
- Simplification of processing in clockwork and projector
- simulations
- Smart Correlation in midPoint 4.6 and Beyond
- Some Thoughts on Associations in 4.9
- Streams and ItemPath performance
- Task archetypes (GUI) open questions
- Task authorizations
- Tuning midPoint on Oracle
- Understanding ApprovalSchemaExecutionInformationType
- Upgrade
- Upgrade process
- User Accesses
- User Notifications
- user-interface
- UX Design notes
- Volatile Attributes (Shadow Items) in 4.9.1 and 4.10
- XML/JSON/YAML vs. XNode vs. internal data
- Archive
- Design Notes
- Developer Zone
- Identity Connectors
- Support
- Trainings
- Evolveum
- Community
- Library
- Case Studies
- Talks
- Glossary
- Frequently Asked Questions
- About
Task authorizations
Last modified 22 Apr 2021 17:31 +02:00
What we want to achieve
We want to specify access to tasks based on a relation of a user to a particular task. The basic relations are:
-
requester,
-
assignee,
-
object (i.e. the subject of approval - e.g. the user whose change is being approved),
-
target (
See MID-3311, MID-3120, MID-3121.
Broader picture
aaa
Was this page helpful?
YES
NO
Thanks for your feedback