securing SMA on Websphere

 securing SMA on Websphere

 

 

  1. Refer to following PDN article for more details:

           https://pdn.pega.com/security/implementing-authentication-for-prsysmgmt-and-prdbutil

          Add the following security contraint entry in your web.xml and repackage the EAR:

          

<security-constraint>
<web-resource-collection>
<web-resource-name>System Management Application - DB utility Application </web-resource-name>
<description>secure all urls for this application</description>
<url-pattern>/*</url-pattern>
<http-method>GET</http-method>
<http-method>POST</http-method>
</web-resource-collection>
<auth-constraint>
<role-name>PegaDiagnosticUser</role-name>
</auth-constraint>
</security-constraint>


<login-config>
<auth-method>BASIC</auth-method>
<realm-name>PegaRULES</realm-name>
</login-config>


<security-role>
<role-name>PegaDiagnosticUser</role-name>
</security-role>

2. Make sure Administrative security is enabled on Websphere and set of users or groups who will have access to SMA configured:

      

        1.png

    3.  Deploy the repackaged war on Websphere and pick an appropriate User or Group

 

        1.png

            1.png

      4. Now when you try and access the prsysmgmt URL, you’ll be prompted for the credentials

Comments

Post a Comment

Popular posts from this blog

Split For Each shape in pega - Parallel processing in Pega

Image
  Split For Each shape in pega Parallel processing in Pega We can allow users to perform multiple tasks independently to complete the work, in pega we can this as parallel processing. In a stage or flow rule, we can add smart shapes to achieve this parallel processing. Smart shapes in pega Pega has defined some smart shapes like  Split Join ,  Split-For-Each,  and  Spin-Off . We have to use these smart shapes in sub-process shape. Each shape can call one or more processes to proceed in parallel. Split For Each shape in pega Split for each allows us to run a single process multiple times by looping through a Page List or Page Group. The main flow continues when processes on the PageList/PageGroup processed. I Will explain with an example:  In a Service Request case type when the user submits a request it should be going for the inspection process. Used Split Join shape to fulfill this requirement with two sub-processes. When all sub-processes are complete, t...
Read more

Queue processor FAQ

Image
  Queue processor FAQ A queue processor rule is an internal background process that you configure for queue management and asynchronous message processing. Use standard queue processor rules for simple queue management or low-throughput scenarios, or use dedicated queue processor rules for higher-scaling throughput, and customized or delayed processing of messages. Best practice is to configure queue processors instead of using standard agents to manage message queuing in Pega Platform. For details, see   Background processing best practices . Frequently Asked Questions about queue processors include the following: How do I queue a message to a queue processor? You can queue a message to a queue processor by performing either of the following actions: Use the   Queue-for-Processing   activity method. Use the   Run in Background   SmartShape when you create a case. For more information, see   Queue-For-Processing method   and   Running a backg...
Read more

Tickets in PEGA – its Configuration, Usage & Execution

Image
Tickets in PEGA – its Configuration, Usage & Execution   What is Ticket in Pega? Tickets are rule instances of class   Rule-Obj-Ticket . A ticket (available under   Process   Category) can be used to jump to or go to another part (either backward or forward) of the current sequence of execution Tickets do not have any processing logic. Why do we need Ticket? In a flow processing, case usually flows through a pre-defined sequence of events. However, there may be certain exceptional scenarios where we need to leave the regular sequence of event and process an exceptional sequence. Tickets are used to process out-of-sequence events. Tickets are entry point to a flow to handle any errors or exceptions or events defined by the user. Business Scenario Let us assume that OSP has a loan processing   application   and the sequence of events is as below: Client applies for a loan by submitting appropriate documents Loan officer reviews the documents and approves ...
Read more