OIDC is just OAuth2 in a ghost costume, so the implementation is nearly trivial.

Apologies, I should have provided more context. We've been futzing with this project which OIDC. We'd be looking to ensure that it works with Dex.

I'm not sure how I'd even test OpenID these days. Offhand, I haven't seen any provider offering OpenID in years.

Would you considered taking prioritized funding for implementing OpenID?

No, we don't want to bring anything upstream if we don't support or maintain it.

@epriestley was just curious if any of the "Real Working Examples" could be brought into the resource folder in phabricator, this information is super useful and helps complete the product.

In T4181#204679, @netroby wrote:

The real working example

[…]
ExecStart=/usr/bin/sudo -u vcs-user  /opt/phabricator/bin/phd start
ExecStop=/usr/bin/sudo -u vcs-user /opt/phabricator/bin/phd stop
[…]

Wow I feel the same way as @lunderwood. The problem is that it now happened for the third time and users send me screenshots of how their upload didn't work. But the permissions are all correctly set up. But then it works again after some time. It's a bit frustrating.

The real working example

An even simpler script below, works now on my Fedora 24 server. Just make sure for your distribution, that the correct database (mysql/mariadb/etc.) service is edited, as well as the rest of the info.

In T4181#133830, @kaismh wrote:

I have created an upstart service for Ubuntu 14.04 LTS. Create a file /etc/init/phd.conf and save the following:

I was not able to use this script in any of my installations, it always causes bootup/shutdown to hang and does not properly start the phd daemons. For some reason, phd for me has been very difficult to get up and running with upstart scripts. Whatever I do, calling service phd start always results in just a hang. If anyone has any insight into how I can do this, would be greatly appreciated. I'm running Ubuntu.

https://secure.phabricator.com/book/phabricator/article/support/

I created the task, then changed the tags manually (selecting only the tags I felt necessary - also removing the BUG tag). Seems I may have found a bug with the bug tracker. ;)

That is, if you go to the Diffusion workboard, we give you a generic create form instead of a choice between the various normal create forms, currently.

You can file stuff without those tags from workboards, and maybe "Support Request" just got caught in the crossfire of typing every possible tag, so that's a legitimate-albeit-unusual pathway here. But I wouldn't expect the short-lived "New Support Request" form to be accessible any longer.

This tracker is for bug reports and feature requests, and we're surprised you were able to file something without either of those tags.

How did you file this task?

In T4181#161779, @sevendays wrote:

@sinayion don't start the phd service before mysql. The daemons need the database to be active.
I'd start phd after http and mysql are up and running.

In T4181#133830, @kaismh wrote:

I have created an upstart service for Ubuntu 14.04 LTS. Create a file /etc/init/phd.conf and save the following:

This was probably implemented in rP51d2d06e3722ad807be588dc894e8d0f0e8be076

I changed the unit file to this:

@sinayion don't start the phd service before mysql. The daemons need the database to be active.
I'd start phd after http and mysql are up and running.

I'm using this unit file, which works when I manually start it or restart it. However, if I do a cold boot of the system the unit fails and I have to ssh in and manually restart it.

OS - Arch Linux

Please be aware I have created an init script for CentOS based systems.