Uploaded image for project: 'Identity Gateway'
  1. Identity Gateway
  2. OPENIG-4514

Introduce Idle timeout at Edge

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 6.5.2
    • Fix Version/s: None
    • Component/s: OpenAM
    • Labels:

      Description

      • Historically, there have been some issues in IG/Agents updating session's idle timeout in AM. Although we provide caching at IG/Agents side, frequent idle timeouts updates in AM leads to CTS performance issues.   
      • Many customers have different idle timeout requirements per application such as App1 need 15 mins idle timeout where as App2 needs 30 mins idle timeout. Currently, idle timeout is driven at AM realm level so same idle timeout applies to all applications in a given realm.

      This RFE is to move idle timeout at edge level so that these rules can be applied at edge level: App1's IG route, App2's IG route etc. This RFE applies to both Agents and IG. 

      Note: Different realms are not recommended for different applications,  realms as they were originally designed to provide separate administrative domains i.e.customers, employees etc. 

       

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            charan.mann Charan Mann
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated: