Râu Cao raucao
  • Joined on 2018-11-24
raucao opened issue kosmos/chef#110 2019-10-26 16:56:29 +00:00
kosmos.social cert renewal failed due to auth error
raucao commented on issue kosmos/chef#107 2019-10-24 12:45:17 +00:00
Set up LDAP server for central account management

By the way I just got Mediawiki to work with LDAP login in my VM, using https://www.mediawiki.org/wiki/Extension:LDAPAuthentication2

raucao commented on issue kosmos/chef#107 2019-10-24 12:44:26 +00:00
Set up LDAP server for central account management

What do you mean by Mastodon creating new accounts? Are you talking about LDAP accounts being created by Mastodon somehow? This is definitely not something that makes any sense

raucao commented on issue kosmos/chef#107 2019-10-24 09:51:12 +00:00
Set up LDAP server for central account management

I think you still don't understand my question. In any case, the point is that Mastodon should never create new accounts, because those accounts then have no information about our other services stored.

raucao commented on issue kosmos/chef#107 2019-10-23 20:02:13 +00:00
Set up LDAP server for central account management

If that's the case, then how are accounts the same between Mastodon and other services?

raucao commented on issue kosmos/chef#107 2019-10-23 09:57:54 +00:00
Set up LDAP server for central account management

On log in with an account and password from LDAP it will find or create the user

raucao commented on issue kosmos/chef#107 2019-10-22 19:42:02 +00:00
Set up LDAP server for central account management

Cool. Does that mean we can actually use the existing accounts? Or that we can at least migrate the existing accounts easily by adding those users to the LDAP directory?

raucao pushed to master at kosmos/chef 2019-10-18 13:52:31 +00:00
77508c62a9 Update barnard node config
raucao commented on issue kosmos/chef#107 2019-10-18 12:37:47 +00:00
Set up LDAP server for central account management

I was thinking more like service=xmpp,service=mastodon and so on. Later, it will also need extra attributes for which namespace of which service it is.

raucao merged pull request kosmos/chef#109 2019-10-18 12:31:40 +00:00
Deploy akkounts-api behind an nginx reverse proxy with a TLS cert
raucao closed pull request kosmos/chef#109 2019-10-18 12:31:40 +00:00
Deploy akkounts-api behind an nginx reverse proxy with a TLS cert
raucao closed issue kosmos/chef#18 2019-10-18 12:31:39 +00:00
Deploy akkounts-api (node.js)
raucao pushed to master at kosmos/chef 2019-10-18 12:31:39 +00:00
9e00070141 Merge branch 'feature/18-akkounts-api' of kosmos/chef into master
2c20fa4a2f Fix the nginx vhost for akkounts-api
f8af66a532 Add/fix akkounts credentials
2104e81250 Add the kosmos-akkounts::nginx recipe to kosmos-akkounts::default
6bb93eb5f5 Fix the path to index.js
Compare 8 commits »
raucao closed issue kosmos/chef#20 2019-10-18 12:31:39 +00:00
Nginx config for akkounts-api
raucao commented on issue kosmos/chef#109 2019-10-18 12:31:18 +00:00
Deploy akkounts-api behind an nginx reverse proxy with a TLS cert

All working in production now! You can try it out yourself.

raucao pushed to feature/18-akkounts-api at kosmos/chef 2019-10-18 11:10:58 +00:00
f8af66a532 Add/fix akkounts credentials
raucao commented on issue kosmos/chef#107 2019-10-18 10:54:54 +00:00
Set up LDAP server for central account management

Not sure what you mean. We can just use attributes to know if a user has access to a certain service or not.

raucao commented on issue kosmos/chef#109 2019-10-18 10:28:30 +00:00
Deploy akkounts-api behind an nginx reverse proxy with a TLS cert

App is now compiled to release dir: https://github.com/67P/akkounts-api/pull/6

raucao pushed to master at kosmos/website 2019-10-17 21:29:08 +00:00
2000fb4382 Update content
raucao commented on issue kosmos/chef#107 2019-10-17 14:19:10 +00:00
Set up LDAP server for central account management

So a decent integration always supports a custom "filter" config, which can be filled with the desired attributes, in order to select users that are allowed to use that service. Saw that in the GitLab doc as well.