anchor.diff:  
   |===
   
  -Select *Add Policy*, and then *Publish* the service. You can see its endpoint information in the *Endpoint* tab, it should be similar to:
  +Select *Add Policy*, and then *Publish* the API. You can see its endpoint information in the *Endpoint* tab, it should be similar to:
   
   https://localhost:8443/apiman-gateway/Newcastle/EchoAPI/1.0
   
  
positive.code: 
  The more observant readers will note that we have already added two of the required elements when we imported the realm into Keycloak; namely, a user `rincewind` and a realm role `echomeister`.
  
  If we navigate back to the *EchoAPI* service in the apiman UI, we can create a *New Version*. We'll call it *_2.0_* and clone the previous configuration. Moving over to the *Policies* tab again, we *Add Policy* and select *Authorization Policy* from the drop-down.
  
  We're going to add two rules:
  
  
negative.code: ---
  layout: post
  title:  "Keycloak and dagger: Securing your APIs with OAuth2"
  date:   2016-01-10 15:25:28 +0100
  author: marc_savy
  categories: gateway security oauth2 keycloak authentication authorization 1.2.x
  