@@ -454,7 +454,8 @@ repository:
454
454
./services start
455
455
` ` `
456
456
457
- > :information_source: **Note:** If you want to clean up and start over again you can do so with the following command:
457
+ > [!NOTE]
458
+ > If you want to clean up and start over again you can do so with the following command:
458
459
>
459
460
> ```console
460
461
> ./services stop
@@ -507,7 +508,7 @@ Once **Authzforce** is running, you can check the status by making an HTTP reque
507
508
(usually `8080`). If the response is blank, this is usually because **Authzforce** is not running or is listening on
508
509
another port.
509
510
510
- # ### :one: Request
511
+ # ### 1️⃣ Request
511
512
512
513
` ` ` console
513
514
curl -X GET \
@@ -556,7 +557,7 @@ can be used to query **Authzforce** about the domains served and policies held.
556
557
557
558
To request domain information from **Authzforce**, make a request to the `/authzforce-ce/domains` endpoint.
558
559
559
- # ### :two: Request
560
+ # ### 2️⃣ Request
560
561
561
562
` ` ` console
562
563
curl -X GET \
@@ -588,7 +589,7 @@ endpoint. The following request obtains information about the `gQqnLOnIEeiBFQJCr
588
589
using a random key by an external Policy Administration Point in this case **Keyrock** has been used as the PAP, and
589
590
pre-generated the rule sets.
590
591
591
- # ### :three: Request
592
+ # ### 3️⃣ Request
592
593
593
594
` ` ` console
594
595
curl -X GET \
@@ -624,7 +625,7 @@ To list the generated IDs for all of the PolicySets found within a domain make a
624
625
` authzforce-ce/domains/{{domain-id}}/pap/policies` endpoint. The following request obtains a list of a given policy IDs
625
626
found within the `gQqnLOnIEeiBFQJCrBIBDA` domain.
626
627
627
- # ### :four: Request
628
+ # ### 4️⃣ Request
628
629
629
630
` ` ` console
630
631
curl -X GET \
@@ -657,7 +658,7 @@ To list the available revisions of a policy, make a request to the
657
658
and can be obtained by drilling down using the previous request. The following request obtains a list revision of a
658
659
given policy found within the `gQqnLOnIEeiBFQJCrBIBDA` domain.
659
660
660
- # ### :five: Request
661
+ # ### 5️⃣ Request
661
662
662
663
` ` ` console
663
664
curl -X GET \
@@ -689,7 +690,7 @@ To obtain a single revision of a `<PolicySet>`, make a request to the
689
690
` authzforce-ce/domains/{{domain-id}}/pap/policies/{{policy-id}}/{{revision-number}}` endpoint. The following request
690
691
obtains the second revision of the given policy found within the `gQqnLOnIEeiBFQJCrBIBDA` domain.
691
692
692
- # ### :six: Request
693
+ # ### 6️⃣ Request
693
694
694
695
` ` ` console
695
696
curl -X GET \
@@ -758,7 +759,7 @@ the Body can be expanded as the rules become more complex.
758
759
To request a decision from Authzforce, make a POST request to the `domains/{domain-id}/pdp` endpoint. In this case the
759
760
user has the `managers-role-0000-0000-000000000000` and is requesting access the `/app/price-change` resource.
760
761
761
- # ### :seven: Request
762
+ # ### 7️⃣ Request
762
763
763
764
` ` ` console
764
765
curl -X POST \
@@ -813,7 +814,7 @@ successful request includes a `<Decision>` element to `Permit` access to the res
813
814
To request a decision from Authzforce, make a POST request to the `domains/{domain-id}/pdp` endpoint. In this case the
814
815
user has the `security-role-0000-0000-000000000000` and is requesting access the `/app/price-change` resource.
815
816
816
- # ### :eight: Request
817
+ # ### 8️⃣ Request
817
818
818
819
` ` ` console
819
820
curl -X POST \
@@ -898,7 +899,7 @@ OAuth2 access grants described in a [previous tutorial](https://github.com/FIWAR
898
899
To log in using the user-credentials flow send a POST request to the `oauth2/token` endpoint of **Keyrock** with the
899
900
` grant_type=password`
900
901
901
- # ### :nine: Request
902
+ # ### 9️⃣ Request
902
903
903
904
` ` ` console
904
905
curl -X POST \
@@ -928,7 +929,7 @@ The response returns an `access_token` to identify the user (in this case Bob th
928
929
If a user has logged in, the `access_token` can be used in combination with the `/user` endpoint to obtain access
929
930
permissions to a resource. This example retrieves Bob's permissions to a given resource.
930
931
931
- # ### :one::zero: Request
932
+ # ### 1️⃣0️⃣ Request
932
933
933
934
` ` ` console
934
935
curl -X GET \
@@ -979,7 +980,7 @@ the User has (`managers-role-0000-0000-000000000000`), the application ID that i
979
980
(`tutorial-dckr-site-0000-xpresswebapp`) and the HTTP verb and resource that are being requested ( a POST request on the
980
981
` /v2/entities` URL)
981
982
982
- # ### :one::one: Request
983
+ # ### 1️⃣1️⃣ Request
983
984
984
985
` ` ` console
985
986
curl -X POST \
0 commit comments