IMAP login can be restricted to a specific domain name.

[kosli]

I have an instance of ownCloud which is used only for one domain and I wanted to make the users able to login via IMAP only with this specific domain name.
If no domain name is given in the configuration file, then the behaviour is the same as before.

This closes #1708.

[karlitschek]

Looks good from my point of view. Not tested.
What do you think @blizzz
👍

[t2d]

Yes, this works. I came up independently with the same solution. Please integrate!
However, you should note, that it changes the paths for f.e. caldav links.
This is a reasonable change, but it could lead to confusion.

[RafaelKa]

👍, but it is to static. It is only for one trusted domain, what about trusted domain list?

[t2d]

But than you run into collisions in namespaces. user1@domain1 and user1@domain2 would both be user1.

[RafaelKa]

@t2d, yes could happen by developing without thinking :-P.
Just using whole Email(incl. Domain) for login ;) ...
Maybe map imap hosts with email-domains, if they are different like :

'user_backends' => [
    [
      'class' => 'OC_User_IMAP',
      'arguments' => [
        '{imap.server1.net:143/imap/tls}', // <- for bc reasons
        [
          '{imap.server1.net:143/imap/tls}' => ['exaple.tld', 'second.tld'],
          '{imap.server2.net:143/imap/tls}' => ['some-cloud.tld', 'some-isp.tld'],
        ]
      ]
    ]
  ],

or if it works without bc:

'user_backends' => [[ 
      'class' => 'OC_User_IMAP', 'arguments' => [
          '{imap.server1.net:143/imap/tls}' => ['exaple.tld', 'second.tld'],
          '{imap.server2.net:143/imap/tls}' => ['some-cloud.tld', 'some-isp.tld']
  ]]],

[kosli]

any update on this?

[PVince81]

I think @RafaelKa gave a 👍 so I guess this means it was tested.
I don't know enough about IMAP and can't test this, so if you all IMAP users/devs agree that this is a good addition, then we can merge this.

[RafaelKa]

notwithstanding, that we do not using composer: Do we need to define ext-imap somewhere as dependency?

And yes, I tested this patch some time ago...

[PVince81]

Usually I think it is possible to specify app dependencies in info.xml. But trouble here is that this app provides different mechanisms, so you can't impose a lib dependencies for users who are only interested in the SMB login plugin for example. Ideal would be to have each auth type in separate apps...

So I'd say no for now.

Since you tested this, I'm merging this then. Thanks!