Adding and validating Non HTTP resource in OpenAM

Tagged: 

This topic contains 3 replies, has 2 voices, and was last updated by  Peter Major 5 days, 3 hours ago.

  • Author
    Posts
  • #18845
     vadivelg 
    Participant

    Is there any way of adding Non HTTP resource to OpenAM server and does it have any rest call for validating the non HTTP resource with a token id.

    #18847
     Peter Major 
    Moderator

    You should be able to define new resource types on the admin console, the only limitation is that you will need to use URIs to describe your resources. Evaluating policies for a different resource type is done the same way as you would evaluate policies for HTTP resources.

    #18866
     vadivelg 
    Participant

    Thanks for the response Peter. Is there a convention for defining URI for a non HTTP resource and Does it follow any pattern ? Could you give us an example.

    #18868
     Peter Major 
    Moderator

    If you want to describe an application as a set of resources for example, you could for example have resources like:
    app://myapp/pages/checkout
    app://myapp/resources/buttons/admin

    if you want to describe doors:
    doors://building01/main/
    doors://building02/staff-kitchen

    So essentially you can come up with whatever you’d like as long as it resembles a hierarchical URL-like structure (where wildcard matching makes sense).

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.

©2017 ForgeRock - we provide an identity and access platform to secure every online relationship for the enterprise market, educational sector and even entire countries. Click to view our privacy policy and terms of use.

Log in with your credentials

Forgot your details?