How to get Remedy OAuth 2 feature benefits with REST API token.

Version 1
    Share This:

    Introduction:

                    The purpose of this document is to provide step by step procedure to get token for long time.

     

    Assumptions:

    • Remedy with REST API configured
    • Remedy SSO is integrated and OAuth 2 is available in RSSO

     

    Problem Statement:

                    While working with remedy REST API, first step is to get authentication token. Authentication token will be used generated using username and password. It will be valid for 5 minutes as default, can be increased to couple of hours or more.

                    How can remedy SSO OAuth2 feature can be utilized, so that client program/integration can work with single token id per client.

     

    Solution:

                    Using Remedy SSO OAuth feature, this problem can be solved. Below is the simple process that needs to be followed:

    1. Register client in Remedy SSO

    2. Authenticate 1 time from client program (Eg. POSTMAN)

    3. Use the token and create change request

    4. Check validity

     

    Please follow below steps to register your program/integration:

    1. Login to RSSO using admin credentials

    2. Click on OAuth2 tab

    3. Click on Client tab

    4. Click on register client

    5.Enter below details and click on SAVE

    6. Once the registration is successful, RSSO will give Client ID and Client Secret. Please save that, since it is not able to retrieve once again.

    Client ID:81b00cc1-46af-4c64-baf0-54d96f1a2bcf

    Secret:MIIEvAIBADANBgkqhkiG9w0BAQEFAASCBKYwggSiAgEAAoIBAQChc5AwkdQd9MAfTYE1R4/iNkhPM+KRZorXH3mKVU9j2pEPx8o8T8pbx1+7NUUp70qXET+iDXiZr02jGZGQE6+mDZQJF30ilQPyNB3je/UKvfvuzsiR+pCOQ3FKD5v+Eu9UVPQXCf1x1CC7GHrKK4w+EPHS9xSH3Jpla31zaevBRRiuGnIo2h7OhWfAGuv6sZTdwYmPEk6GZR8LbK2pzQzjv6zD0x9J7ICLm1m13TFfUYvZE3rAIMjXNPk8KXV3yT+dBQh2zzJXLJ+IU3VhJixmtNduyfQ2nMyZDibKrO9QL93r+b3Iahk2ioXYEwEFsOn1piVxA6OHFIt1AZ6z/w1zAgMBAAECggEAHQAhGlhXfboE+Jp3ZxafpcaSXoe3Xt7IebPRpSOFyy3reKYukX7TnoDFlV8QOWQeRdx3TaiVzSVMEMv69aJTnsQ5nxh1Bc02lD8AT2hor7FIm7DRHkefx64dn2wGXTERhFhuL+U/fT7ZUkInbEE+Q7fPeFGhgnYB1c3lDuIr0t9JOFYO8SqZvQTiIpp73iUGlvRJq2dJwLIfaoJabSmLQSlJQwBDuaeEY23jLAS9kGVpnt63FdVoSEOPptIGYjFfRpgT575uyuiR4og+qJCUllWhznffnjcB5aMT1aL2TpQjBDCIPNuQh7CYJJ/WgYUWr5S3EqUCm1Vi5Poi62/wIQKBgQDb8IuaWvVW0Yl5B48GWCgj4xvgQgNklKfg//WxYUkH8+baoSn3kOjq+AkurIzJqlkI+uVet1MsBomc6r33B9537fBaBGLWJXI+foV/bR6QZlUJEaMtHVIctGelj2e3OzG8pkvETRDrE702UPevhY+N7XaqxyCAQ/DoeYVYyrQOFQKBgQC77Bx41RR5L+ajqb7RLfTEI2GJpRE8wWCvzw7XwniHLuZsylYyumwY3IC23lhJUvWvDPioVLs2ZWtA89+YF+R8LkS6+hIZtS2IBw/Ih2aSt7FPGd/s+rPZznKhDYq43/cMpj5y+JzTQHCWTtO/a98SVxhIfJDSW5Ua4n9+awOXZwKBgCYbYGTHG7kGJxaEO8Cyp4nIQL0zUtkrdIbkclJgc8Hf/YCl6dqODf0gKp8eoGoUjMakifdGNi/rlg5NEcrqXx5SaJGALwvBgzDWxRSV+HS2dkdS+f3IFcEJdOfXl/XEWNLB0WDapXLFgcQWdUPBFWVW3neqdrQikWwGGhePT3EdAoGAYefBbbKV2A18vAfTwmeO/iDw0CWPtXeKSA44TXCkGsn0gvlnr0Ywy0MWTC/LD2iJV4oKgqiiYNS17EEiXLsV7xyr8j4W8A3Uiuoi7vacGhRZ7DwuzehPi0pjrkS/4VHOBGkYYA3mpqkL/0NSToiEz6lQnXNIgE/2futCQTq/xEECgYAdgRottTKmWh4/Cm5ZtUz/Qxt0y+FMpz+PvyGM6K4tunhDvCF3HoA9TVL1NyBuf4uAzkWvJFKIYBEnzz0W1rykfwEUkvLU2u4DVLx8IkR996DbXcDTuJrNboXC0Mi9y5XFYrpUEY6LMnCz/4kDNpx+AVCV7005fsGjhqy9LCSvoA==

     

    7. Once the data is copied, Click on Back to list

     

    8. Now open POSTMAN, Select Type as OAuth 2.0

    9. Click on “Get New Access Token” and provide the information as below:

    Token Name: XXXPostmanClient

    Auth URL: https://<RSSO SERVER FQDN NAME>/rsso/oauth2/authorize

    Access Token URL: https://<RSSO SERVER FQDN NAME>/rsso/oauth2/token

    Client ID: <Which has been stored while registering the client>

    Client Secret: <Which has been stored while registering the client>

    Leave other options as default.

     

    10. Click on request token

    11. RSSO login screen will be populated asking for username and password. Please enter credentials for which user token will be generated.

    12. Check user and details and click on OK

    13. Postman will have below screen

    14. Add the token to header and start examples

    getPeopleData:

    createIncident:

    getIncidentID:

    getEntryID:

    updateIncident:

    15. Validation in RSSO and POSTMAN (Eg: 8 hours token as per the configuration):

    RSSO Configuration:

    Postman validation:

    Conclusion: Using Remedy SSO OAuth 2.0 feature, client programs can be registered and token can be generated with long hours or maximum (Days) validation.

     

    NOTE: Please find the attached POSTMAN file, which have all the examples shown in this above.