Skip to content
  • A place to talk about whatever you want

    4k Topics
    24k Posts
    K
    Ah, got it, thank you!
  • Stay tuned here to hear more about new releases and features of NodeBB!

    3k Topics
    18k Posts
    Brutus5000B
    Hi @julian, as a long term user of the sso-skeleton plugin (which is btw currently broken, see my fixing PR) I am very interested in switching to a more generalized solution so I can finally stop carrying forward the plugin fork over the versions of NodeBB. So currently it seems to me that there are some pieces missing, so I'm here to question you what is the eventual goal. On that depends if I rather contribute to the new plugin or try to fix the old plugin. No-code user info parsing Update: existing OIDC mapping is sufficient. So I found that there are some predefined ways on how to use OIDC userinfo endpoints. But as it claims to be an OAuth2 plugin and some providers like Github do not follow it, there is a need to map the data from the userinfo-alike endpoint into the nodebb specific fields (username, email, isAdmin). I was thinking about adding a solution that allows a configuring json in the admin panel that allows mapping the user-response into a uniform nodebb format, for example using JSONata syntax: Assuming the endpoints returns a json like this { "user": "Brutus5000", "email": "[email protected]", "id": 12345, "roles": ["administrators"] } Now being able to map this into a structured json without having to create any hooks using jsonata (making up the specified JSON structure here) { "user": user, "email": email, "externalId": id, "isAdmin": "administrators" in roles } Consistently storing and querying external user ids So the user comes from an external service. And we create a user. Awesome. Unfortunately looking them up via username and email is not unique, as any of them can change in the external system (and in our system both do). So why not carry along the external user id from that system. Furthermore we need a querying a user via it's external system in order to allow the leading system to change username and/or email. The rest can be done using the internal write API. Being able to skip email verification In my system emails are supposed to be in sync. It would actually be harmful to send out verification emails for newly registered users, so this should be configurable. present with pre-defined json format I am willing to help implementing parts of these, even though I have very little JS frontend skills. But it has to be aligned with your goals, as I might need a little guidance on the way.
  • You have a cool idea about NodeBB? Post it here.

    826 Topics
    5k Posts
    barisB
    It looks like this and yeah it is for registered users. [image: 1730513433494-11b8f777-e10c-49ec-b70d-2912e8029ad3-image.png]
  • Discussion regarding NodeBB Plugin development.

    2k Topics
    15k Posts
    T
    @phenomlab Oh thanks alot! That's great help. Real nice plugin of yours.
  • A public listing of community themes created by the NodeBB community.
    48 Topics
    1k Posts
    N
    It looks like the discussion content in this topics has become outdated, so should I refer to the docs site directly instead? I want to customize the default home page and post detail page, which involves layout and style customization, so, am I correct to develop a new theme for this?
  • Need help with installing or configuring NodeBB? Look here.

    5k Topics
    27k Posts
    phenomlabP
    @julian Perfect, thanks. This one has been driving me nuts!
Online Users