feature: ability to share auth data between caddy instances (high availability)

[hurrycaner]

A clear and concise description of what you want the system to do.

There was a PR in caddy-auth-portal implementing this (branch implement-oauth-for-ha-systems. Would be nice to implement that: greenpau/caddy-auth-portal#174

[greenpau]

@hurrycaner , thank you for the issue! 👍

[hurrycaner]

@greenpau i'm thinking about developing this feature since i really need this feature, i need to support redis as a cache implementation to oauth, but i would like to know from you what i need to implement to make this a valuable feature for this plugin :)

[greenpau]

Closing and moving to backlog for now.

[hurrycaner]

@greenpau why did you closed this one? I just started working at this...

[greenpau]

why did you closed this one? I just started working at this...

@hurrycaner , once you have your proposal ready (prior to coding), please post it here and I will reopen. There are changes happening right now related to backends: https://twitter.com/GreenbergTech/status/1507346211359100929

[hurrycaner]

Hey @greenpau, the idea is to bring the PR greenpau/caddy-auth-portal#174 to go-authcrunch repository, considering your comments here. Is there anything else i should consider?

[greenpau]

@hurrycaner , I am interested to see how your are planning to integrate that code in go-authcrunch. For example, I don’t want to create dependencies to external libraries (i.e. want to keep things pure), unless absolutely necessary.

1. What would Caddyfile look like?

2. What would it “attach” to, etc.

[hurrycaner]

@greenpau thank you for your quick responses :)

{
  security {
    cache <type> {
      <configurations>
      ...
    }
  }
}

2. Well, each cache implementation would depend on some library, in the PR mentioned before, gomemcache was used, i was thinking about using https://github.com/eko/gocache, so the responsibility of handling cache won't be another thing to handle and maintain and will minimize dependencies, because it will interface cache handling, including for in-memory.