When the users change their Facebook password, the page access token gets invalidated. To overcome this, ask the user to reauthorize the Facebook connection

Acceptance Criteria

• Run a cronjob every day to find the invalid token, mark the integration as invalid/needs-reauthorization
• If the flag is set, show a message in the frontend to reauthorize

https://developers.faceboo

Right now we only set the ip and last_seen_at fields when a customer record is created. Let's update the customer update_metadata endpoint (https://github.com/papercups-io/papercups/blob/master/lib/chat_api_web/controllers/customer_controller.ex#L58) so that it also handles this.

(I think we can just default the last_seen_at field to the current timestamp for now.)

I'm submitting a ...

• bug report

What is the current behavior? [REQUIRED]

• If username in DB is lower-case but user used upper case to log-in, the server rejects his first packet due to ticket mismatch.

Steps to reproduce [REQUIRED]

1. Create user with lower-case (eg. helloworld)
2. Login with upper-case (eg. Helloworld)

What is the expected behavior? [REQUIRED]

User

When .spec.host is blank, OpenShift generates a route automatically. This is quite convenient. However, when Tailor is used, drift is detected in subsequent comparisons, as the live config has a value then, but the template does not. It would be nice to make use of the applied-configuration annotation to allow .spec.host to be blank, and not show any drift unless the template values has chan