auth

Paddy 2015-07-15 Parent:8ecb60d29b0d

178:0a2c3d677161 Go to Latest

auth/sql/postgres_init.sql

Update to use a generic event emitter. Rather can creating a purpose-built event emitter for each and every event we need to emit (I'm looking at you, login verification event) which is _downright silly_, we're now using a generic event publisher that's based on saying "HEY A MODEL UPDATED". This means we need to change all our setup code in authd to use events.NewNSQPublisher or events.NewStdoutPublisher instead of our homegrown solutions. Which also means updating our config to take an events.Publisher instead of our LoginVerificationNotifier (blergh). Our Context also now uses an events.Publisher instead of a LoginVerificationNotifier. Party all around! We also replaced our SendLoginVerification helper method on Context with a SendModelEvent helper method on Context, which is just a light wrapper around events.PublishModelEvent. Of course, all this means we need to update our email_verification listener to listen to the correct channel (based on the model we want updates about) and filter down to a Created action or our new custom action for "the customer wants their verification resent", which I'm OK making a special case and not generic, because c'mon. But we had a subtle change to all our constants, some of which are unofficial constants now. I'm unsure how I feel about this. We also updated our email_verification listener so that we're unmarshalling to a custom loginEvent, which is just an events.Event that overwrites the Data property to be an auth.Login instance. This is to make sure we don't need to wrangle a map[string]interface{}, which is no fun. I'm also OK with special-casing like this, because it's 1) a tiny amount of code, 2) properly utilising composition, and 3) the only way I can think of to cleanly accomplish what I want. I also added a note about GetLogin's deficient handling of logins, namely that it doesn't recognise admins and return Verification codes to them, which would be a useful property for internal tools to take advantage of. Ah well. I updated the Profile and Login implementations so they're now event.Model instances, mainly by just exporting some strings from them through getters that will let us automatically build an Event from them. This lets us use the PublishModelEvent helper. I updated our CreateProfileHandler to properly mangle the login Verification property, and to fire off the ActionCreated events for the new Login and the new Profile. I updated our GetLoginHandler and UpdateLoginHandler to properly mangle the loginVerification property. God that's annoying. :-/ You'll note I didn't start publishing the events.ActionUpdated or events.ActionDeleted events for Profiles or Logins yet, and didn't bother publishing any events for literally any other type. That's because I'm a lazy piece of crap and will end up publishing them when I absolutely have to. Part of that is because if a channel isn't created/being read for a topic, the messages will just stack up in NSQ, and I don't want that. But mostly I'm lazy. Finally, I got to delete the entire profile_verification.go file, because we're no longer special-casing that. Hooray!

Download raw file
View source Diff to previous Annotate
History
1 CREATE TABLE IF NOT EXISTS profiles (
2 id VARCHAR(36) PRIMARY KEY,
3 name VARCHAR(64) NOT NULL,
4 passphrase VARCHAR(64) NOT NULL,
5 iterations INTEGER NOT NULL,
6 salt VARCHAR(64) NOT NULL,
7 passphrase_scheme INTEGER NOT NULL,
8 compromised BOOLEAN NOT NULL,
9 locked_until TIMESTAMPTZ NOT NULL,
10 passphrase_reset VARCHAR(64) NOT NULL,
11 passphrase_reset_created TIMESTAMPTZ NOT NULL,
12 created TIMESTAMPTZ NOT NULL,
13 last_seen TIMESTAMPTZ NOT NULL
14 );
15
16 CREATE TABLE IF NOT EXISTS logins (
17 type VARCHAR(16) NOT NULL,
18 value VARCHAR(64) PRIMARY KEY,
19 profile_id VARCHAR(36) NOT NULL,
20 created TIMESTAMPTZ NOT NULL,
21 last_used TIMESTAMPTZ NOT NULL,
22 verification VARCHAR(36) NOT NULL,
23 verified BOOLEAN NOT NULL
24 );
25
26 CREATE TABLE IF NOT EXISTS clients (
27 id VARCHAR(36) PRIMARY KEY,
28 secret VARCHAR(64) NOT NULL,
29 owner_id VARCHAR(36) NOT NULL,
30 name VARCHAR(32) NOT NULL,
31 logo VARCHAR(512) NOT NULL,
32 website VARCHAR(140) NOT NULL,
33 type VARCHAR(16) NOT NULL,
34 deleted BOOLEAN NOT NULL
35 );
36
37 CREATE TABLE IF NOT EXISTS endpoints (
38 id VARCHAR(36) PRIMARY KEY,
39 client_id VARCHAR(36) NOT NULL,
40 uri VARCHAR(512) NOT NULL,
41 normalized_uri VARCHAR(512) NOT NULL,
42 added TIMESTAMPTZ NOT NULL
43 );
44
45 CREATE TABLE IF NOT EXISTS scopes (
46 id VARCHAR(64) PRIMARY KEY,
47 name VARCHAR(64) NOT NULL,
48 description TEXT NOT NULL
49 );
50
51 CREATE TABLE IF NOT EXISTS sessions (
52 id VARCHAR(72) PRIMARY KEY,
53 ip VARCHAR(32) NOT NULL,
54 user_agent TEXT NOT NULL,
55 profile_id VARCHAR(36) NOT NULL,
56 login VARCHAR(64) NOT NULL,
57 created TIMESTAMPTZ NOT NULL,
58 expires TIMESTAMPTZ NOT NULL,
59 active BOOLEAN NOT NULL,
60 csrftoken VARCHAR(72) NOT NULL
61 );
62
63 CREATE TABLE IF NOT EXISTS tokens (
64 access_token TEXT PRIMARY KEY,
65 refresh_token VARCHAR(36) UNIQUE NOT NULL,
66 created TIMESTAMPTZ NOT NULL,
67 created_from VARCHAR(128) NOT NULL,
68 expires_in INTEGER NOT NULL,
69 token_type VARCHAR(64) NOT NULL,
70 profile_id VARCHAR(36) NOT NULL,
71 client_id VARCHAR(36) NOT NULL,
72 revoked BOOLEAN NOT NULL,
73 scopes varchar(64)[] NOT NULL
74 );
75
76 CREATE TABLE IF NOT EXISTS authorization_codes (
77 code VARCHAR(36) PRIMARY KEY,
78 created TIMESTAMPTZ NOT NULL,
79 expires_in INTEGER NOT NULL,
80 client_id VARCHAR(36) NOT NULL,
81 redirect_uri TEXT NOT NULL,
82 state TEXT NOT NULL,
83 profile_id VARCHAR(36) NOT NULL,
84 used BOOLEAN NOT NULL,
85 scopes varchar(64)[] NOT NULL
86 );