xenithorb

#!/bin/bash
#
# /etc/kernel/postinst.d script to sign akmods kmods after kernel upgrade
#
# Author: Michael Goodwin  Date: 2016-09-21

# 1. Copy this script to /etc/kernel/postinst.d/ and `chmod +x` it
#
# 2. Create signing keys (store these somewhere useful and safe):
#    $ mkdir -p /etc/pki/tls/private/mok

jhass

Setup

1. Copy 99-u2f_lock_screen.rules to /etc/udev/rules.d.
2. Copy gnome_lock_all_sessions to /usr/local/bin.
3. Mark gnome_lock_all_sessions as executable: chmod +x /usr/local/bin/gnome_lock_all_sessions
4. Reload udev: udevadm control -R

pulkitsinghal

Pitfalls

The REST adapter for strong-remoting sets up its own error handler! So you cannot accomplish this for REST API related calls by replacing:

1. app.use(loopback.errorHandler()); in server/server.js
2. or, loopback#errorHandler in middleware.json

So don't waste your time there.

Deeper Understanding

danvbe

I have managed to install this… and make it work. I implemented it for Facebook and Google, but you can extend it. My solution it is mostly as described in #116, with a bit of more code presented. The key aspects that lack in the #116 presentation (IMO) are:

• the registration as service of your custom FOSUBUserProvider (with the necessary parameters)
• set the service for oauth_user_provider in the security.yml with your custom created service

Here are the steps:

1. Routing. In routing.yml I have added all the routes for both bundles.
2. Configuration. I have set the config.yml mostly as it is presented in the HWIOAuthBundle.
3. Security. I have set the security.yml mostly as it is presented in the HWIOAuthBundle (though my routes are using /login pattern, not /connect). Also, the oauth_user_provider is set for my custom service.