Merge pull request #26 from tonyxrmdavidson/solutionPatternsLinksCopy…

…fieldsIDs

Solution patterns links copyfieldsIds

walkthroughs/1-connecting-apps-asynchronous-messaging/walkthrough.adoc

@@ -113,7 +113,7 @@ To create a table for storing the orders, you will use PostgreSQL.
 
 Follow these steps to create a table.
 
-. Log in to link:{openshift-host}/k8s/cluster/projects/{walkthrough-namespace}[OpenShift Namespace, window="_blank"] for this walkthrough.
+. Log in to link:{openshift-host}/k8s/cluster/projects/{walkthrough-namespace}[OpenShift Namespace, window="_blank", id="{task-context}-1"] for this walkthrough.
 . Select *Workloads > Pods* from the vertical navigation menu on the left.
 . Click the Pod that has the name *rhmi-lab-orders-db* followed by an ID, for example *rhmi-lab-orders-db-1-cfqh2*.
 . Select the *Terminal* tab on the Pod details screen.
@@ -174,7 +174,7 @@ To create a connector for the Fuse RESTful API, register the OpenAPI definition
 
 Follow these steps to create an API Connector.
 
-. Log in to the link:{fuse-url}[Red Hat Fuse Online, window="_blank", id="{task-context}-1"] console.
+. Log in to the link:{fuse-url}[Red Hat Fuse Online, window="_blank", id="creating-connections-1"] console.
 +
 NOTE: You are not logging into the shared Fuse Online instance, available from the link:/[All services tab].
 Starting this Solution Pattern provisioned an instance of Fuse Online which is not shared with other cluster users.
@@ -206,7 +206,7 @@ Order System REST API Connector {user-sanitized-username}
 .. Click *Save*.
 
 [type=verification]
-Is the new connector *Order System REST API Connector {user-sanitized-username}* displayed on the *Customizations > API Client Connectors* screen of the link:{fuse-url}[Red Hat Fuse Online, window="_blank", id="{task-context}-2"] console?
+Is the new connector *Order System REST API Connector {user-sanitized-username}* displayed on the *Customizations > API Client Connectors* screen of the link:{fuse-url}[Red Hat Fuse Online, window="_blank", id="creating-connections-2"] console?
 
 [type=verificationFail]
 {standard-fail-text}
@@ -224,7 +224,7 @@ To enable Fuse Online to send messages from the queue to the {retrieve-messages-
 
 Follow these steps to create a connection to the CRUD App.
 
-. Log in to the link:{fuse-url}[Red Hat Fuse Online, window="_blank", id="{task-context}-3"] console.
+. Log in to the link:{fuse-url}[Red Hat Fuse Online, window="_blank", id="creating-connections-3"] console.
 . Select *Connections* from the left hand menu.
 . Select the *Create Connection* button to start the *Create Connection* wizard.
 . When prompted with *Select connector*, select *Order System REST API Connector {user-sanitized-username}*.
@@ -249,7 +249,7 @@ Order System REST API Connection {user-sanitized-username}
 
 
 [type=verification]
-Is the new connection displayed on the *Connections* screen of the link:{fuse-url}[Red Hat Fuse Online, window="_blank", id="{task-context}-4"] console?
+Is the new connection displayed on the *Connections* screen of the link:{fuse-url}[Red Hat Fuse Online, window="_blank", id="creating-connections-4"] console?
 
 [type=verificationFail]
 {standard-fail-text}
@@ -268,7 +268,7 @@ To allow Fuse Online to consume messages placed on the queue by the {create-mess
 
 Follow these steps to create an AMQP connection.
 
-. Log in to the link:{fuse-url}[Red Hat Fuse Online, window="_blank", id="{task-context}-5"] console.
+. Log in to the link:{fuse-url}[Red Hat Fuse Online, window="_blank", id="creating-connections-5"] console.
 . Select *Connections* from the left hand menu.
 . Select the *Create Connection* button to start the *Create Connection* wizard.
 . Select *AMQP Message Broker* to configure an *AMQP* connection.
@@ -303,7 +303,7 @@ Incoming Order Queue Connection {user-sanitized-username}
 . Click *Save*.
 
 [type=verification]
-Is the new connection displayed on the *Connections* screen of the link:{fuse-url}[Red Hat Fuse Online, window="_blank", id="{task-context}-6"] console?
+Is the new connection displayed on the *Connections* screen of the link:{fuse-url}[Red Hat Fuse Online, window="_blank", id="creating-connections-6"] console?
 
 
 [type=verificationFail]
@@ -332,7 +332,7 @@ Is the new connection displayed on the *Connections* screen of the link:{fuse-ur
 
 Follow these steps to create an integration.
 
-. Log in to the link:{fuse-url}[Red Hat Fuse Online, window="_blank", id="wt1a_2_3_1_fuse-url"] console.
+. Log in to the link:{fuse-url}[Red Hat Fuse Online, window="_blank", id="{task-context}-1"] console.
 . Select *Integrations* from the left hand menu.
 . Select the *Create Integration* button to start the *Create Integration* wizard.
 . Choose *Incoming Order Queue Connection {user-sanitized-username}* as the *Start Connection*.
@@ -391,7 +391,7 @@ Integration Solution 1 {user-sanitized-username}
 The integration may take some time to complete building.
 
 [type=verification]
-Is the integration displayed as *Running* on the *Integrations* screen of the link:{fuse-url}[Red Hat Fuse Online, window="_blank", id="{task-context}-1"] console?
+Is the integration displayed as *Running* on the *Integrations* screen of the link:{fuse-url}[Red Hat Fuse Online, window="_blank", id="{task-context}-2"] console?
 
 [type=verificationFail]
 

walkthroughs/2-protecting-apps-sso/walkthrough.adoc

@@ -69,14 +69,15 @@ Realms are isolated from one another and can only manage and authenticate the us
 
 ****
 *What is Customer Application SSO?*
+:task-context: creating-a-client
 
 Customer Application SSO, included with Red Hat Managed Integration, enables you to define the identities of your end users.
 Red Hat manages this instance, however there are some additional users with admin level privileges who can configure this instance.
 ****
 
 Follow these steps to create a client.
 
-. Go to the link:{sso-realm-url}[Master, window="_blank"] realm, which is running on your {customer-sso-name} service.
+. Go to the link:{sso-realm-url}[Master, window="_blank", id="creating-a-client-1"] realm, which is running on your {customer-sso-name} service.
 .. If prompted, log in with your username and password. You will see the *Master* realm if the login is successful.
 .. Hover the realms dropdown in the top left and click on *Add Realm*.
 .. Enter *realm-{user-username}* as the name and click *Create*. You will be redirected to your new realm.
@@ -85,7 +86,7 @@ Follow these steps to create a client.
 . On the *Add Client* screen:
 .. In the *Client ID* field, enter
 +
-[subs="attributes+"]
+[subs="attributes+", id="creating_a_client"]
 ----
 {client-name}
 ----
@@ -103,12 +104,13 @@ In the *Settings* tab on the *Client* page, make sure the *Enabled* toggle is se
 
 [time=7]
 == Creating a user
+:task-context: creating-a-user
 
 To secure your application with single sign-on and allow additional users to log in to your instance, you need to create users in a realm.
 
 Follow these steps to create a new user and set that user's password.
 
-. Go to the link:{sso-user-realm-url}[{realm-name}, window="_blank"] realm, which is running on your {customer-sso-name} service.
+. Go to the link:{sso-user-realm-url}[{realm-name}, window="_blank", id="{task-context}-1"] realm, which is running on your {customer-sso-name} service.
 .. If prompted, log in with your username and password.
 . You will see the *{realm-name}* realm if the login is successful.
 . Select *Users* from the vertical navigation menu on the left side of the screen.
@@ -138,6 +140,7 @@ Do you see the *customer* username listed in the table?
 
 [time=15]
 == Enabling SSO in the Order Entry System
+:task-context: enabling-sso
 
 === Obtaining the SSO configuration
 
@@ -158,7 +161,7 @@ The *{create-messages-app}* is run from a Node.js server, so the Node.js
 demonstrate how to include a configuration and enable the adapter.
 
 
-. Go to link:{sso-user-realm-url}[SSO Realm, window="_blank"].
+. Go to link:{sso-user-realm-url}[SSO Realm, window="_blank", id="enabling-sso-1"].
 . If prompted, log in with your username and password.
 . Select *Clients* from the side menu.
 . Click the `{client-name}` client that was created earlier.
@@ -168,7 +171,7 @@ demonstrate how to include a configuration and enable the adapter.
 
 === Creating a SSO Config Map Entry
 
-. Login to the link:{openshift-console-url}[OpenShift Console, window="_blank"].
+. Login to the link:{openshift-console-url}[OpenShift Console, window="_blank", id="enabling-sso-2"].
 . Select the project that contains the pods from *{sp1-title}*.
 . Select *Workloads > Config Maps*.
 . Click the *Create Config Map*  button.
@@ -177,14 +180,14 @@ demonstrate how to include a configuration and enable the adapter.
 .. Remove all the lines below *data*.
 .. Add a line `KEYCLOAK_CONFIG: |` under *data*. Make sure it is indented with one tab.
 +
-NOTE: the pipe symbol (`|`) allows for multiline input, see link:https://yaml.org/spec/1.2/spec.html#id2795688[the yaml spec] for more details.
+NOTE: the pipe symbol (`|`) allows for multiline input, see link:https://yaml.org/spec/1.2/spec.html#id2795688[the yaml spec, id="enabling-sso-3"] for more details.
 
 .. Paste the contents of the _keycloak.json_ file in the next line. Make sure all lines are indented with two tabs.
 . Click the *Create* button.
 
 === Applying the SSO Config Map
 
-. Log in to the link:{openshift-console-url}[OpenShift Console, window="_blank"].
+. Log in to the link:{openshift-console-url}[OpenShift Console, window="_blank", id="enabling-sso-4"].
 . Select the project that contains the pods from *{sp1-title}*.
 . Select *Workloads > Deployment Configs*.
 . Select the *rhmi-lab-nodejs-order-frontend* item from the *Deployment Configs* list.