Bug 1473782 - Automate Domain Switches if user Switches Groups after a Request
Summary: Automate Domain Switches if user Switches Groups after a Request
Keywords:
Status: CLOSED DUPLICATE of bug 1467364
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Automate
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: GA
: cfme-future
Assignee: Lucy Fu
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-21 16:10 UTC by myoder
Modified: 2020-09-10 11:00 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-27 18:27:16 UTC
Category: Bug
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description myoder 2017-07-21 16:10:56 UTC
Description of problem:
We have users belonging to several groups and have one automation domain per tenant.  These automation domains contain some variables (remote system hostname, user / password) to access third party API (exemple LDAP server).

If a user submits a provision request, when a user switches his current group, the automation domain of the request is also switched and so we are forced to ask them to not switch their current group during the processing of a request.

Version-Release number of selected component (if applicable):
CFME 5.7 (will update with the full buid soon)

How reproducible:
customer environment

Steps to Reproduce:
1. Have a user submit a provision request
2. Have user switch groups before the provision request is finished
3.

Actual results:
The automate domain of the request is switched to correlate to the "current" group the user belongs to.

Expected results:
The automate domain should remain the same automate domain as when the provision request was initially requested.

Additional info:

Comment 3 Lucy Fu 2017-07-27 18:27:16 UTC

*** This bug has been marked as a duplicate of bug 1467364 ***


Note You need to log in before you can comment on or make changes to this bug.