That all depends on your SASL backend service; you should be able to connect it to whatever you want.
However actually doing that can be complicated. You'll have to find tutorials online, since it isn't memcached specific. On Tue, 1 Oct 2019, Jiuming Shao wrote: > Hi there, > I have a quick question on SASL configuration and mechanism choice. > I noticed that for SASL DB, I always need to pass in a username and password > (either in a db file or using `saslpasswd2`) as the credential to auth > connection. I am wondering if > there is any plugins or mechanisms which can accept dynamic credential. > I don't want to store anything on disk nor send any credential in plain text > on wire. I already have a credential provider daemon ready, I can always > query it for the latest > credential that I should use(shared by both cache client and cache server.). > > Thanks in advance! > > Jiuming > > -- > > --- > You received this message because you are subscribed to the Google Groups > "memcached" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to memcached+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/memcached/7427f813-b2c5-417e-b018-4b493443eff5%40googlegroups.com. > > -- --- You received this message because you are subscribed to the Google Groups "memcached" group. To unsubscribe from this group and stop receiving emails from it, send an email to memcached+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/memcached/alpine.DEB.2.21.1910011220210.31828%40dskull.
