• Icon: Suggestion Suggestion
    • Resolution: Won't Fix
    • None
    • None
    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      When RSS feeds are generated, there's the opportunity to have "token authentication". In this case, an opaque token is added to the end of the feed URL. People accessing the feed with this token will retrieve it with the same credentials as the person who created the feed.

      Tokens, obviously, must not be transferrable between different feeds, not be predictable, and not be able to have either the original username or password retrieved from them.

            [CONFSERVER-4329] Token-based authentication for RSS

            Sen Geronimo made changes -
            Workflow Original: JAC Suggestion Workflow 4 [ 3570343 ] New: JAC Suggestion Workflow 3 [ 4340308 ]

            Please consider a token based authentication for reading RSS feeds

            Johannes Fürtler added a comment - Please consider a token based authentication for reading RSS feeds
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow 2 [ 3173750 ] New: JAC Suggestion Workflow 4 [ 3570343 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3029384 ] New: JAC Suggestion Workflow 2 [ 3173750 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2533022 ] New: JAC Suggestion Workflow [ 3029384 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 [ 2291210 ] New: Confluence Workflow - Public Facing v4 [ 2533022 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 - TEMP [ 2185606 ] New: Confluence Workflow - Public Facing v3 [ 2291210 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 [ 1917276 ] New: Confluence Workflow - Public Facing v3 - TEMP [ 2185606 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v2 [ 1747943 ] New: Confluence Workflow - Public Facing v3 [ 1917276 ]
            jonah (Inactive) made changes -
            Description Original: When RSS feeds are generated, there's the opportunity to have "token authentication". In this case, an opaque token is added to the end of the feed URL. People accessing the feed with this token will retrieve it with the same credentials as the person who created the feed.

            Tokens, obviously, must not be transferrable between different feeds, not be predictable, and not be able to have either the original username or password retrieved from them.
            New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *Confluence Server*. Using *Confluence Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/CONFCLOUD-4329].
              {panel}

            When RSS feeds are generated, there's the opportunity to have "token authentication". In this case, an opaque token is added to the end of the feed URL. People accessing the feed with this token will retrieve it with the same credentials as the person who created the feed.

            Tokens, obviously, must not be transferrable between different feeds, not be predictable, and not be able to have either the original username or password retrieved from them.

              Unassigned Unassigned
              cmiller@atlassian.com Charles Miller (Inactive)
              Votes:
              52 Vote for this issue
              Watchers:
              39 Start watching this issue

                Created:
                Updated:
                Resolved: