Hi there,
Is there a way that we can make the n8n self-hosted community version to work with an external authentication system (SSO)?
I know this is the enterprise feature, but I was wondering if that can be done at least for testing purposes on the community version.
Thanks,
A
If the goal is to externalize login/access to n8n, there aren’t really any ways to circumvent the enterprise feature that provides that function.
There is an API to create users, but that doesn’t appear to support any kind of update (for sync w/ SSO) or even password initialization. So, that wouldn’t be very useful.
Community also has a limitation of 1 admin user, and doesn’t allow sharing workflows between regular, non-admin users. Admin can see everything but regular users can’t see anything but their own workflows. Sharing is also enterprise feature.
Is there some other utility you wanted from this, other than centralizing login/credentials?
Thanks for your reply @hubschrauber!
At this stage (testing), I’m only interested in integrating the n8n with our sso for demo purposes; hence, I am asking about incorporating it with the community version.
So per your comment, there is no way that I can make this work?
Appreciate your comment on this 
We asked the same question a while back about the possibility of getting a license that would enable all of the enterprise features for trial/demo purposes, but limit n8n in other ways to make it impractical for anything other than development (similar to the Confluent (Kafka) platform developer license). However, the part of n8n that deals with licensing restrictions doesn’t, afaik, currently support anything like that, so that wasn’t an option.
Maybe if the n8n sales team were asked about this often enough, they would prioritize making it possible to run n8n that way. I suspect there are some other cases where the inability to conveniently verify whether enterprise features work, in a particular environment, resulted in a shrug on getting an enterprise license, or even a pass on n8n altogether. Ultimately, though, that’s still a business decision the n8n team is making, so, as they say… it is what it is.
I would recommend evaluating n8n on all of its other capabilities, most of which are available in the Community edition, and make sensible assumptions about how the enterprise features work, including SSO integration. If you have a specific SSO solution, I don’t think the n8n sales or technical team would have any problem answering specific questions about what would be (or wouldn’t be) supported. Here’s the contact info.