laurenhall1526-netizen commented on issue #43430:
URL: https://github.com/apache/airflow/issues/43430#issuecomment-4117277332

   Hi @potiuk,
   The root cause seems to be a mismatch between the API security layer and
   the FAB auth manager: route dependencies pass granular *Details objects,
   but the FAB auth manager ignores them.
   I understand this issue is about syncing permissions handling and docs, not
   enabling fine-grained entity-level access.
   
   On Mon, Mar 23, 2026, 11:08 AM Pierre Jeambrun ***@***.***>
   wrote:
   
   > *pierrejeambrun* left a comment (apache/airflow#43430)
   > <https://github.com/apache/airflow/issues/43430#issuecomment-4111788157>
   >
   > @ThyTran1402 <https://github.com/ThyTran1402> what do you mean?
   >
   > In AF3 yes read/write/etc... on entities (pool, connections, ... etc...)
   > are 'global'. Not set at the entity level, which is expected. People are
   > free to write their own custom auth manager if they need a fine grained
   > entity based access control. (for now it's dag level based).
   >
   > This issue is not about that but just syncing the permissions and the docs.
   >
   > —
   > Reply to this email directly, view it on GitHub
   > 
<https://github.com/apache/airflow/issues/43430?email_source=notifications&email_token=B7IHA45MGIRM22HOVUMPMCT4SFOO3A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJRGE3TQOBRGU32M4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#issuecomment-4111788157>,
   > or unsubscribe
   > 
<https://github.com/notifications/unsubscribe-auth/B7IHA43O44JS6JFU2TZRPSL4SFOO3AVCNFSM6AAAAACJODR5KSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCMJRG44DQMJVG4>
   > .
   > You are receiving this because you are subscribed to this thread.Message
   > ID: ***@***.***>
   >
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to