#2523 Changes to target.agent.approve.list parameter is not reflected in the TPS Web UI
Closed: Fixed None Opened 7 years ago by rpattath.

Changes to target.agent.approve.list parameter is not reflected in the TPS Web
UI

Steps to Reproduce:

1. In TPS CS.cfg add a paramter to agent approval list,
target.agent_approve.list=Profiles,Profile_Mappings
target.configure.list=Profiles,Subsystem_Connections,Profile_Mappings,Authentic
ation_Sources

2. Restart TPS
3. Login to TPS Web UI as Agent user

Actual results:

Profile Mapping is not listed under System menu

Expected results:

Profile Mapping is not listed under System menu to make approval for changes

Per PKI Bug Council of 10/18/2016: 10.3

Fixed in master:

  • f979c3b436e9a12e8c71ba0abab5c892d375f945
  • 3c4f9c7eb1aa9a71c0f5a943314d355d2fdeebb4

Per PKI Bug Council of 11/03/2016: REOPEN 10.3

Patch separation issue; see corresponding bugs.

master:

commit 54496a801f235cd1eafd6d600387046aaa1bffcd
Author: Matthew Harmsen <mharmsen@redhat.com>
Date:   Thu Nov 3 16:10:55 2016 -0600

    Revert "Fixed TPS UI system menu."

    This reverts commit f979c3b436e9a12e8c71ba0abab5c892d375f945.

commit 3231f58709116a3d2f8725aa519c36bd9a0bf898
Author: Matthew Harmsen <mharmsen@redhat.com>
Date:   Thu Nov 3 16:10:37 2016 -0600

    Revert "Fixed TPS UI for agent approval."

    This reverts commit 3c4f9c7eb1aa9a71c0f5a943314d355d2fdeebb4.

DOGTAG_10_3_BRANCH:

commit 0b80470b85eb3560eceba3caaa34456bca0150e9
Author: Matthew Harmsen <mharmsen@redhat.com>
Date:   Thu Nov 3 16:13:49 2016 -0600

    Revert "Fixed TPS UI system menu."

    This reverts commit 7126177723750b5fa71b5414c1fb4b488c4c710f.

commit 891491ac993045047af051a87ba385a8f5b38da9
Author: Matthew Harmsen <mharmsen@redhat.com>
Date:   Thu Nov 3 16:13:37 2016 -0600

    Revert "Fixed TPS UI for agent approval."

    This reverts commit 43392ef555b007f81e2d2567c84da261778b9c2a.

The changes have been split and pushed to master.

Common changes:

  • 6d5d15edebeb1ba113e4f3d5b2bb1ba93a92ce1d

TPS changes:

  • 3d3772025d0b6cf527dac6e40102bb5d6f4ce317
  • 0e7062a19cb5cf261469e59204c1035c2fbb7d94

Replying to [comment:9 edewata]:

The changes have been split and pushed to master.

Common changes:
* 6d5d15edebeb1ba113e4f3d5b2bb1ba93a92ce1d

Cherry-picked into DOGTAG_10_3_BRANCH:

  • 388e443b99999dd2aa0832aaed0cdf43ee260b81

TPS changes:
3d3772025d0b6cf527dac6e40102bb5d6f4ce317
0e7062a19cb5cf261469e59204c1035c2fbb7d94

Cherry-picked into DOGTAG_10_3_BRANCH:

  • e14afabab406fdc2a36baab5b3682aa3499a285e
  • ab6f48c0f871601a3bf121f5f734b4261e74edfd

Metadata Update from @rpattath:
- Issue assigned to edewata
- Issue set to the milestone: 10.3.9

7 years ago

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/2643

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Login to comment on this ticket.

Metadata