Skip to content

Support project_domain_name instead of user_domain_name in iaas_filter#12

Open
rajivmucheli wants to merge 3 commits intostable/2024.2-m3from
support_pn
Open

Support project_domain_name instead of user_domain_name in iaas_filter#12
rajivmucheli wants to merge 3 commits intostable/2024.2-m3from
support_pn

Conversation

@rajivmucheli
Copy link

also move the if iaas_filter above since its applied to all domains

fix imageproxy error in show(), .get is not supported

also move the if iaas_filter above since its applied to all domains

fix imageproxy error in show(), .get is not supported
@rajivmucheli rajivmucheli changed the title Support project_domain_name instead of user_domain_name Support project_domain_name instead of user_domain_name in iaas_filter Jul 25, 2025
# starts with 'iaas' as a hard tenant-level policy enforcement.
user_domain_name = getattr(req.context, 'user_domain_name', None)
LOG.debug("[IAAS_FILTER] Effective user_domain_name: %s", user_domain_name)
project_domain_name = getattr(req.context, 'project_domain_name', None)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did you check that the context always contains this value? Because it didn't for me, so I had to use the context''s project_id to fetch the domain from Keystone.

If we rely on this being there, but it isn't always, then some users (maybe application credentials? idk) can circumvent this check.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, as discussed internally.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants