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. Traccar
  3. Issues Setting Up OpenID

Issues Setting Up OpenID

Scheduled Pinned Locked Moved Solved Traccar
16 Posts 3 Posters 2.0k Views 3 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.
  • girishG girish

    @TheMoodBoardz I guess you are trying to set up a non-Cloudron OIDC provider ? If so, when you install the app, install it with Cloudron SSO disabled i.e "Leave user management to the app" . When you install it that way, Cloudron will leave the OpenID configuration alone.

    T Offline
    T Offline
    TheMoodBoardz
    wrote on last edited by
    #3

    @girish Yes that's what I want to do - I've set it to "Leave user management to the app" however it still will remove the config for some reason?

    girishG 1 Reply Last reply
    0
    • nebulonN nebulon marked this topic as a question on
    • T TheMoodBoardz

      @girish Yes that's what I want to do - I've set it to "Leave user management to the app" however it still will remove the config for some reason?

      girishG Offline
      girishG Offline
      girish
      Staff
      wrote on last edited by
      #4

      @TheMoodBoardz it shouldn't. Just checking if we have some bug in the package.

      T 1 Reply Last reply
      0
      • girishG girish

        @TheMoodBoardz it shouldn't. Just checking if we have some bug in the package.

        T Offline
        T Offline
        TheMoodBoardz
        wrote on last edited by
        #5

        @girish Ok, Thanks

        1 Reply Last reply
        0
        • girishG Offline
          girishG Offline
          girish
          Staff
          wrote on last edited by
          #6

          @TheMoodBoardz thanks for reporting, this was a bug. It's fixed in the latest package. If you update to latest and setup oidc, it won't be overwritten after restart anymore.

          1 Reply Last reply
          1
          • T Offline
            T Offline
            TheMoodBoardz
            wrote on last edited by
            #7

            Brilliant, Will give that a go and will come back once I have the results

            1 Reply Last reply
            1
            • T Offline
              T Offline
              TheMoodBoardz
              wrote on last edited by
              #8

              I've tested however though it does not remove it from config - it won't give the option at login via OpenID button. I have also checked my build that does use login via Cloudron and I have realised that never had the button to login via OpenID

              1 Reply Last reply
              0
              • girishG Offline
                girishG Offline
                girish
                Staff
                wrote on last edited by
                #9

                @TheMoodBoardz could be that your openid configuration is not correct.

                The app uses something like this:

                    <entry key='openid.clientId'>##CLOUDRON_OIDC_CLIENT_ID##</entry>
                    <entry key='openid.clientSecret'>##CLOUDRON_OIDC_CLIENT_SECRET##</entry>
                    <entry key='openid.issuerUrl'>##CLOUDRON_OIDC_ISSUER##</entry>
                    <entry key='openid.authUrl'>##CLOUDRON_OIDC_AUTH_ENDPOINT##</entry>
                    <entry key='openid.tokenUrl'>##CLOUDRON_OIDC_TOKEN_ENDPOINT##</entry>
                    <entry key='openid.userInfoUrl'>##CLOUDRON_OIDC_PROFILE_ENDPOINT##</entry>
                
                
                T 1 Reply Last reply
                0
                • girishG girish

                  @TheMoodBoardz could be that your openid configuration is not correct.

                  The app uses something like this:

                      <entry key='openid.clientId'>##CLOUDRON_OIDC_CLIENT_ID##</entry>
                      <entry key='openid.clientSecret'>##CLOUDRON_OIDC_CLIENT_SECRET##</entry>
                      <entry key='openid.issuerUrl'>##CLOUDRON_OIDC_ISSUER##</entry>
                      <entry key='openid.authUrl'>##CLOUDRON_OIDC_AUTH_ENDPOINT##</entry>
                      <entry key='openid.tokenUrl'>##CLOUDRON_OIDC_TOKEN_ENDPOINT##</entry>
                      <entry key='openid.userInfoUrl'>##CLOUDRON_OIDC_PROFILE_ENDPOINT##</entry>
                  
                  
                  T Offline
                  T Offline
                  TheMoodBoardz
                  wrote on last edited by
                  #10

                  @girish So I am using the same config as you have shown, but it does not give you the option. I have just installed a fresh version and still have the same issue of it not giving you the option to sign in using OpenID

                  1 Reply Last reply
                  0
                  • T Offline
                    T Offline
                    TheMoodBoardz
                    wrote on last edited by
                    #11

                    @girish I have just rest tested it with coping it like for a working build now, and I now get this error:

                    <!DOCTYPE><html><head><title>Error</title></head><html><body>500 - Server Error</body></html>

                    1 Reply Last reply
                    0
                    • nebulonN Away
                      nebulonN Away
                      nebulon
                      Staff
                      wrote on last edited by
                      #12

                      anything in the app logs? Maybe some typo or otherwise wrong formatting of the configs?

                      1 Reply Last reply
                      0
                      • girishG Offline
                        girishG Offline
                        girish
                        Staff
                        wrote on last edited by girish
                        #13

                        Right, I have seen the 500 error when the xml configuration is incorrect somewhere. traccar is not clear at times when giving error messages.

                        edit: to be clear, even when the values are incorrect. not the xml format/syntax itself.

                        T 1 Reply Last reply
                        0
                        • girishG girish

                          Right, I have seen the 500 error when the xml configuration is incorrect somewhere. traccar is not clear at times when giving error messages.

                          edit: to be clear, even when the values are incorrect. not the xml format/syntax itself.

                          T Offline
                          T Offline
                          TheMoodBoardz
                          wrote on last edited by
                          #14

                          @girish Yeah it's not very helpful error message.

                          @nebulon the config is as below (I have removed the actual URLs);

                          <entry key="openid.clientId">CLIENTID</entry>
                          <entry key="openid.clientSecret">CLIENTSECRET</entry>
                          <entry key="openid.issuerUrl">https://DOMAIN/application/o/traccar/</entry>
                          <entry key="openid.authUrl">https://DOMAIN/application/o/authorize/</entry>
                          <entry key="openid.tokenUrl">https://DOMAIN/application/o/token/</entry>
                          <entry key="openid.userInfoUrl">https://DOMAIN/application/o/userinfo/</entry>

                          girishG 1 Reply Last reply
                          0
                          • T TheMoodBoardz

                            @girish Yeah it's not very helpful error message.

                            @nebulon the config is as below (I have removed the actual URLs);

                            <entry key="openid.clientId">CLIENTID</entry>
                            <entry key="openid.clientSecret">CLIENTSECRET</entry>
                            <entry key="openid.issuerUrl">https://DOMAIN/application/o/traccar/</entry>
                            <entry key="openid.authUrl">https://DOMAIN/application/o/authorize/</entry>
                            <entry key="openid.tokenUrl">https://DOMAIN/application/o/token/</entry>
                            <entry key="openid.userInfoUrl">https://DOMAIN/application/o/userinfo/</entry>

                            girishG Offline
                            girishG Offline
                            girish
                            Staff
                            wrote on last edited by
                            #15

                            @TheMoodBoardz check the logs for the actual error. It throws an error even when the URLs are unreachable. Like java.net.ConnectException , java.nio.channels.UnresolvedAddressException etc...

                            Atleast, for me, I could create an OIDC client separately in the User Directory view of Cloudron and then put in the values below and then I get the OIDC login button. Note that if you get even the domain name wrong, it throws an error!

                              <entry key="openid.clientId">cid-xx</entry>
                              <entry key="openid.clientSecret">yy</entry>
                              <entry key="openid.issuerUrl">https://my.smartserver.io/openid</entry>
                              <entry key="openid.authUrl">https://my.smartserver.io/openid/auth</entry>
                              <entry key="openid.tokenUrl">https://my.smartserver.io/openid/token</entry>
                              <entry key="openid.userInfoUrl">https://my.smartserver.io/openid/me</entry>
                            
                            1 Reply Last reply
                            1
                            • girishG girish marked this topic as a regular topic on
                            • T Offline
                              T Offline
                              TheMoodBoardz
                              wrote on last edited by
                              #16

                              @girish So after running a few tests it seems that Traccar does not like the domain to have a "/" at the end, no error logs to support this, but it does track with what was happening - typically my SSO system will want this, so I have made some changes, and it is all working now.

                              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