Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. BookStack
  3. OIDC Login Button not picking up Cloudron Branding

OIDC Login Button not picking up Cloudron Branding

Scheduled Pinned Locked Moved Solved BookStack
3 Posts 2 Posters 92 Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • N Offline
    N Offline
    Neiluj
    wrote on last edited by
    #1

    Hi,

    Could it be that the OIDC login button for Bookstack does not pick up automatically the branding of the cloudron instance it is installed on?
    There is definitely a manual entry (OIDC_NAME=XXX) in the env file which can be set for this though.

    No biggy - Just mentioning as this might have been overlooked.

    1 Reply Last reply
    0
    • J Offline
      J Offline
      joseph
      Staff
      wrote on last edited by
      #2

      @Neiluj maybe the migration went wrong but works here on a fresh install.

      OIDC_NAME=${CLOUDRON_OIDC_PROVIDER_NAME}
      

      that picks the env var

      N 1 Reply Last reply
      0
      • J joseph

        @Neiluj maybe the migration went wrong but works here on a fresh install.

        OIDC_NAME=${CLOUDRON_OIDC_PROVIDER_NAME}
        

        that picks the env var

        N Offline
        N Offline
        Neiluj
        wrote on last edited by
        #3

        @joseph Thanks for checking - This all sounds good.
        It is indeed an old instance which has been running, so it could be something that did not work during the migration.

        1 Reply Last reply
        1
        • nebulonN nebulon marked this topic as a question on
        • nebulonN nebulon has marked this topic as solved on
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Bookmarks
        • Search