Different logins for users and streamers

[ringtailedfox]

Question

Is there a way to incorporate the old version (around v1.4.0) configuration of having different usernames/passwords for users and for streamers?

This is how it used to look and function:

  ###############################################
  # Default path settings -> Authentication

  # Username required to publish.
  # SHA256-hashed values can be inserted with the "sha256:" prefix.
  publishUser: mystream
  # Password required to publish.
  # SHA256-hashed values can be inserted with the "sha256:" prefix.
  publishPass: streamerpasswordgoeshere
  # IPs or networks (x.x.x.x/24) allowed to publish.
  publishIPs: []

  # Username required to read.
  # SHA256-hashed values can be inserted with the "sha256:" prefix.
  readUser: vieweruser
  # password required to read.
  # SHA256-hashed values can be inserted with the "sha256:" prefix.
  readPass: viewerpasswordgoeshere
  # IPs or networks (x.x.x.x/24) allowed to read.
  readIPs: []

Right now, the same user/password combination works for both streamers and users, which i think is a fairly serious security risk...

how would i go about re-implementing this functionality with version 1.8.2? is it even possible?

if this is a bug or you guys think this is a feature request, i'll head over to the issues tab and duplicate this over there...

[ringtailedfox]

An update: i figured out a way to accomplish what i needed, using the new format:

# Internal authentication.
# list of users.
authInternalUsers:
  # Default unprivileged user.
  # Username. 'any' means any user, including anonymous ones.
- user: streamerpassword
  # Password. Not used in case of 'any' user.
  pass: streamerpasswordgoeshere
  # IPs or networks allowed to use this user. An empty list means any IP.
  ips: []
  # List of permissions.
  permissions:
    # Available actions are: publish, read, playback, api, metrics, pprof.
  - action: publish
    # Paths can be set to further restrict access to a specific path.
    # An empty path means any path.
    # Regular expressions can be used by using a tilde as prefix.
    path:
  - action: read
    path:
  - action: playback
    path:
  # Default unprivileged user.
  # Username. 'any' means any user, including anonymous ones.
- user: viewer
  # Password. Not used in case of 'any' user.
  pass: viewerpasswordgosehere
  # IPs or networks allowed to use this user. An empty list means any IP.
  ips: []
  # List of permissions.
  permissions:
    # Available actions are: publish, read, playback, api, metrics, pprof.
  - action: read
    # Paths can be set to further restrict access to a specific path.
    # An empty path means any path.
    # Regular expressions can be used by using a tilde as prefix.
    path:
  - action: playback
    path:

This seems to work great for having a password-protected, SSL-enrcypted stream :D

[bluenviron-bot]

This discussion is being locked automatically because the last update was more than 2 years ago.

Do not use the content of this discussion as reference since it's probably outdated!

The official documentation is the only place in which you can find up-to-date answers.