8 ms·

Show HN: Keratin AuthN – Accounts and Auth Microservice in Go

104 points by cainlevy 9y ago

praxxis 9y ago
We're currently using this as our auth layer for https://empatico.org https://empatico.org, so it's production ready!
krullie 9y ago
How does it compare to Hydra/Dex? What I'm missing is a page that tells me where it sits in the ecosystem. A versus page if you will.
- cainlevy 9y ago
  I'd love to fill that in! If anyone would like a comparison, please add links in this thread and I'll reply. Later, I can collect it into a published page.
  - krullie 9y ago
    That would be great, thanks! Here are the links to the projects I mentioned. https://github.com/coreos/dex https://github.com/coreos/dex https://github.com/ory/hydra https://github.com/ory/hydra
    - cainlevy 9y ago
      > Dex is NOT a user-management system, but acts as a portal to other identity providers through "connectors." > ORY Hydra is not an identity provider (user sign up, user log in, password reset flow), but connects to your existing identity provider through a consent app. AuthN IS all the things that Dex and Hydra say they are not. I'll bet it could integrate with both given a bit of investment, e.g. by satisfying the "consent app" expectations. AuthN does use as much of the OpenID Connect protocol as I could manage though. I started there and streamlined down to optimize for API-driven interactions rather than the redirect-driven interactions that are common with OAuth and OIC.
  - rtomayko 9y ago
    https://auth0.com https://auth0.com I've just started dabbling on a small project and would be interested to understand how features overlap and differences in license/distribution model.
    - cainlevy 9y ago
      Auth0 is top-notch SaaS. I have only good things to say about their product. Aside from being OSS, one major difference is that Keratin AuthN is purely an API. It's optimized for customization so that it will fit with any bespoke (secure) UX you want to provide. I found Auth0's API to be something of an after-thought, second to their hosted/branded/templatable pages.
- danesparza 9y ago
  From the Dex README: "Dex is NOT a user-management system, but acts as a portal to other identity providers through "connectors." This lets dex defer authentication to LDAP servers, SAML providers, or established identity providers like GitHub, Google, and Active Directory." It seems like AuthN IS a user management system. So that's a big difference right there.
- mindcrash 9y ago
  Hydra and Dex both support OAuth and OpenID Connect. This apparently supports neither, but comes with its own JWT structure. With inbound federation that shouldn't be much of a problem, but with outbound federation you'll have some very difficult questions to answer (especially because all major identity solutions are pretty much OIC centric these days)
  - cainlevy 9y ago
    Yeah, I don't expect this JWT scheme to become an adopted standard. It's been streamlined from OIC for the narrow use case of working tightly with a trusted app. Adding support for inbound federation is on the roadmap. Support for outbound federation using OIC isn't out of the question either, but I don't yet see the motivation.
galvanium 9y ago
Is SAML supported and if not is it planned in the near future ?
- cainlevy 9y ago
  I'm currently investing in JWT and have not done enough research on SAML to make it part of my plans. Happy to learn more.
  - galvanium 9y ago
    You might want to take a look at AWS-Cognito and their SAML and OAuth2.0 integration. For our enterprise startup, we are leaning towards Cognito to provide multi-tenant UserPools with customer specified authentication providers.
rmetzler 9y ago
Today I was evaluating what I we should use for something like this, a unified Facade with an API. We evaluated Traefik and Kong. Decision was for Kong, since we need more features like auth, logging, rate limit.
- cainlevy 9y ago
  Strong choice! My dream is for AuthN to provide authentication and account functionality for folks who have not yet invested in an API gateway, and then seamlessly plug in when their architecture matures later. Extracting user accounts can be a difficult barrier for transitions like that.
ehc 9y ago
Has Keratin gone through any security research / penetration testing?
- cainlevy 9y ago
  I would dearly love that! The answer is not yet. Can you recommend any testers that are OSS-friendly? My current plan is to set up a HackerOne page. I know that bug bounties don't replace good penetration testing, but it's a start.
je42 9y ago
almost no test coverage. did i miss them ? for proper use in production you would need to have hundreds of unittests and a whole bunch of component + integration and e2e tests.
- praxxis 9y ago
  There are tests - they're colocated with the source, not in a separate tests folder, e.g. https://github.com/keratin/authn-server/tree/master/services https://github.com/keratin/authn-server/tree/master/services
- cainlevy 9y ago
  Tests are colocated inside packages (folders) using a `_test.go` convention. Service tests[1] are the main unit tests, and use mock implementations of the data store interfaces. Data (DAO) tests[2] are generally run across every implementation using only the public interface. This helps me stay sane with the mock implementations. The API tests[3] are integration tests, and use Go's excellent httptest package to boot a real server and execute real HTTP commands. [1] https://github.com/keratin/authn-server/tree/master/services https://github.com/keratin/authn-server/tree/master/services [2] https://github.com/keratin/authn-server/tree/master/data https://github.com/keratin/authn-server/tree/master/data [3] https://github.com/keratin/authn-server/tree/master/api/accounts https://github.com/keratin/authn-server/tree/master/api/acco...
- Lord_Zero 9y ago
  Check the make file: https://github.com/keratin/authn-server/blob/master/Makefile#L51 https://github.com/keratin/authn-server/blob/master/Makefile... Notice it runs "go test $(shell glide nv)" `glide nv` is a command that gets you all packages except the vendor directory https://github.com/Masterminds/glide#glide-novendor-aliased-to-nv https://github.com/Masterminds/glide#glide-novendor-aliased-... then read the go doc for test https://golang.org/cmd/go/#hdr-Test_packages https://golang.org/cmd/go/#hdr-Test_packages: > 'Go test' recompiles each package along with any files with names matching the file pattern "*_test.go".
- plexicle 9y ago
  Yeah, you missed them.
brianolson 9y ago
It's just name/pass It would be much more interesting to me if it also did Oauth2 login with Google/Facebook/Twitter/etc.
- cainlevy 9y ago
  Yeah, name/pass sounds pretty simple, doesn't it? But doing it correctly, securely, with a service architecture? That gets interesting. > It would be much more interesting to me if it also did Oauth2 login with Google/Facebook/Twitter/etc. Totally agreed. The reason I designed AuthN around accounts first is because I believe that's the best way to launch an app. OAuth2 and OIC logins are powerful, but they're secondary to the classic login.
ahoka 9y ago
"Microservices perform better, especially when written in Go." Nonsense.
- ShabbosGoy 9y ago
  Sort of agree, that's a very noisy and broad statement. I'd argue that the underlying I/O and event loop implementation matters more. At the end of the day it's all about highly available systems. Am I wrong?
  - ahoka 9y ago
    You are right. Architecture is all that matters unless you are in some very special niche.
  - andrewstuart2 9y ago
    Microservices need to be divided up very carefully, with full knowledge of the latency trade-off of moving functionality across a network gap. A same-datacenter round-trip takes 5,000 times longer than a main memory access, and 1,000,000 times longer than an L1 cache access. There's no silver bullet in performance or scalability. Each solution will require trading off advantages that matter less to achieve business goals. Here are a few references that leap to mind (I keep the first printed out and pinned right next to my monitor). https://gist.github.com/jboner/2841832 https://gist.github.com/jboner/2841832 https://www.quora.com/What-are-some-mind-blowing-facts-about-computers/answer/Thomas-Cormen-1 https://www.quora.com/What-are-some-mind-blowing-facts-about...
    - sealthedeal 9y ago
      The latency you speak of is not noticeable to an end user, unless that end user is an HFT client. Great reference though.
    - mentat 9y ago
      The gain is decoupling deploy and implementation, not latency performance (or network reliability).
kuschku 9y ago
Am I missing something, or does this really have no support for TOTP/HOTP? An authentication system without 2FA or U2F support in 2017 seems... lacking (or unfinished).
- cainlevy 9y ago
  It's on my roadmap. Prioritizing is hard. :/
nmenglund 9y ago
How does AuthN compare to Keycloak? http://www.keycloak.org http://www.keycloak.org
- cainlevy 9y ago
  Keycloak does some really great things. It does require managing a Java runtime though, and is missing the streamlining that allows AuthN to run as an invisible API. Keycloak (and similar) hosts and renders your login page. You customize through theming. You're expected to redirect users through a standard OAuth2/OIDC flow on a different domain. AuthN doesn't render any HTML. That's all you, from start to finish. This means you have control over the UX and can build the login page directly into your own app, just like you would when using an auth library in a typical monolith.
  - guywhocodes 9y ago
    What, I can't simply post to any login/register/logout uri's and expect either a redirect with configuring headers back or an object that let's me manage the token manually? EDIT: I've been trying out keycloak and it looks great but I've always assumed I just had not figured out how to make that happen. As the documentation is quite large and of the harder kind.
  - artpar 9y ago
    You can design the login/register page in keycloak completely. From scratch. I have used it before and had done that.
cortesi 9y ago
This looks pretty reasonable! I would love to see a Cloud Storage backend. A minor quibble is that I think that managing your own metrics in Redis is probably not the simplest or most flexible approach - instead, you should consider exposing a /metrics endpoint that can be ingested by the user's monitoring tool of choice (Prometheus/InfluxDB/etc).
- cainlevy 9y ago
  Thanks! Have you seen the /stats endpoint? It exposes the metrics as JSON, which may be a good match for your suggestion. I'd also like to export the key events to a STATSD-compatible sink so a sophisticated user can manage metrics in their own system. Redis is already on hand because of other features though, and HLL is a pretty cheap integration. I figure it's a decent starting point for many people.
  - cortesi 9y ago
    It looks like the /stats endpoint consults the Redis database and returns processed data. If we're aggregating metrics externally, it would be more idiomatic for this to be totally stateless and just expose hot metrics - it's the aggregator's job to store and process the data. This can be quite painless using something like the Go Prometheus library. Being tied to Redis is also not great. For instance, it looks like everything apart from the metrics could comfortably live in Google Cloud Storage if you had a backend for it. Cloud Storage really isn't an appropriate place to put frequently updated counters, though. So if I deployed AuthN, I would want to be able to ditch Redis. I should stress, though, that these are quibbles. I think AuthN looks very nice, and the quibbles are cropping up because I'm trying to figure out if I can use it. :)
    - cainlevy 9y ago
      That all sounds like a direction I'd happily consider: * Google Cloud Storage implementations for data interfaces * Metrics interface with a Prometheus implementation (STATSD to follow) * Redis-backed HLL metrics are optional Feel free to open issues in the tracker if you reach that point!
tetraodonpuffer 9y ago
the toplevel links (implementation / deployment / configuration) don't work for me, they go to say /keratin/authn-server/docs/config.md which is a 404 presumably instead of /keratin/authn-server/blob/master/docs/config.md
- cainlevy 9y ago
  Fixed, thanks!
  - tetraodonpuffer 9y ago
    no problem, btw, the first time I did make test I got this, but after that I was not able to repro it again and make test always worked, pasting here in case you are interested Creating authnserver_server_1 ... done TEST_REDIS_URL=redis://127.0.0.1:8701/12 \ TEST_MYSQL_URL=mysql://root@127.0.0.1:8702/authnservertest \ go test ./data/... ./models/... ./tokens/... ./ops/... ./config/... ./lib/... ./api/... ./services/... . [mysql] 2017/11/08 13:27:23 packets.go:33: unexpected EOF [mysql] 2017/11/08 13:27:23 packets.go:33: unexpected EOF [mysql] 2017/11/08 13:27:23 packets.go:33: unexpected EOF --- FAIL: TestAccountStore (0.01s) --- FAIL: TestAccountStore/MySQL (0.00s) Error Trace: account_store_test.go:43 Error: Received unexpected error driver: bad connection Connect github.com/keratin/authn-server/data/mysql.ensureDB /home/luser/go/external/src/github.com/keratin/authn-server/data/mysql/db.go:71 github.com/keratin/authn-server/data/mysql.TestDB /home/luser/go/external/src/github.com/keratin/authn-server/data/mysql/db.go:27 github.com/keratin/authn-server/data_test.TestAccountStore.func3 /home/luser/go/external/src/github.com/keratin/authn-server/data/account_store_test.go:42 testing.tRunner /usr/local/stow/go-1.9.0/go/src/testing/testing.go:746 runtime.goexit /usr/local/stow/go-1.9.0/go/src/runtime/asm_amd64.s:2337 ensureDB github.com/keratin/authn-server/data/mysql.TestDB /home/luser/go/external/src/github.com/keratin/authn-server/data/mysql/db.go:29 github.com/keratin/authn-server/data_test.TestAccountStore.func3 /home/luser/go/external/src/github.com/keratin/authn-server/data/account_store_test.go:42 testing.tRunner /usr/local/stow/go-1.9.0/go/src/testing/testing.go:746 runtime.goexit /usr/local/stow/go-1.9.0/go/src/runtime/asm_amd64.s:2337 FAIL FAIL github.com/keratin/authn-server/data 0.040s ? github.com/keratin/authn-server/data/mock [no test files] ? github.com/keratin/authn-server/data/mysql [no test files] ok github.com/keratin/authn-server/data/redis 0.771s ? github.com/keratin/authn-server/data/sqlite3 [no test files]
xena 9y ago
Is there an API client for this in Go?
- cainlevy 9y ago
  Seems like an oversight, doesn't it? I've created an issue to track here: https://github.com/keratin/authn-server/issues/15 https://github.com/keratin/authn-server/issues/15

104 points by cainlevy 9y ago

We're currently using this as our auth layer for https://empatico.org https://empatico.org, so it's production ready!

How does it compare to Hydra/Dex? What I'm missing is a page that tells me where it sits in the ecosystem. A versus page if you will.

cainlevy 9y ago
I'd love to fill that in! If anyone would like a comparison, please add links in this thread and I'll reply. Later, I can collect it into a published page.
- krullie 9y ago
  That would be great, thanks! Here are the links to the projects I mentioned. https://github.com/coreos/dex https://github.com/coreos/dex https://github.com/ory/hydra https://github.com/ory/hydra
  - cainlevy 9y ago
    > Dex is NOT a user-management system, but acts as a portal to other identity providers through "connectors." > ORY Hydra is not an identity provider (user sign up, user log in, password reset flow), but connects to your existing identity provider through a consent app. AuthN IS all the things that Dex and Hydra say they are not. I'll bet it could integrate with both given a bit of investment, e.g. by satisfying the "consent app" expectations. AuthN does use as much of the OpenID Connect protocol as I could manage though. I started there and streamlined down to optimize for API-driven interactions rather than the redirect-driven interactions that are common with OAuth and OIC.
- rtomayko 9y ago
  https://auth0.com https://auth0.com I've just started dabbling on a small project and would be interested to understand how features overlap and differences in license/distribution model.
  - cainlevy 9y ago
    Auth0 is top-notch SaaS. I have only good things to say about their product. Aside from being OSS, one major difference is that Keratin AuthN is purely an API. It's optimized for customization so that it will fit with any bespoke (secure) UX you want to provide. I found Auth0's API to be something of an after-thought, second to their hosted/branded/templatable pages.
danesparza 9y ago
From the Dex README: "Dex is NOT a user-management system, but acts as a portal to other identity providers through "connectors." This lets dex defer authentication to LDAP servers, SAML providers, or established identity providers like GitHub, Google, and Active Directory." It seems like AuthN IS a user management system. So that's a big difference right there.
mindcrash 9y ago
Hydra and Dex both support OAuth and OpenID Connect. This apparently supports neither, but comes with its own JWT structure. With inbound federation that shouldn't be much of a problem, but with outbound federation you'll have some very difficult questions to answer (especially because all major identity solutions are pretty much OIC centric these days)
- cainlevy 9y ago
  Yeah, I don't expect this JWT scheme to become an adopted standard. It's been streamlined from OIC for the narrow use case of working tightly with a trusted app. Adding support for inbound federation is on the roadmap. Support for outbound federation using OIC isn't out of the question either, but I don't yet see the motivation.

galvanium 9y ago

Is SAML supported and if not is it planned in the near future ?

cainlevy 9y ago
I'm currently investing in JWT and have not done enough research on SAML to make it part of my plans. Happy to learn more.
- galvanium 9y ago
  You might want to take a look at AWS-Cognito and their SAML and OAuth2.0 integration. For our enterprise startup, we are leaning towards Cognito to provide multi-tenant UserPools with customer specified authentication providers.

rmetzler 9y ago

Today I was evaluating what I we should use for something like this, a unified Facade with an API. We evaluated Traefik and Kong. Decision was for Kong, since we need more features like auth, logging, rate limit.

cainlevy 9y ago
Strong choice! My dream is for AuthN to provide authentication and account functionality for folks who have not yet invested in an API gateway, and then seamlessly plug in when their architecture matures later. Extracting user accounts can be a difficult barrier for transitions like that.

ehc 9y ago

Has Keratin gone through any security research / penetration testing?

cainlevy 9y ago
I would dearly love that! The answer is not yet. Can you recommend any testers that are OSS-friendly? My current plan is to set up a HackerOne page. I know that bug bounties don't replace good penetration testing, but it's a start.

je42 9y ago

almost no test coverage. did i miss them ? for proper use in production you would need to have hundreds of unittests and a whole bunch of component + integration and e2e tests.

praxxis 9y ago
There are tests - they're colocated with the source, not in a separate tests folder, e.g. https://github.com/keratin/authn-server/tree/master/services https://github.com/keratin/authn-server/tree/master/services
cainlevy 9y ago
Tests are colocated inside packages (folders) using a `_test.go` convention. Service tests[1] are the main unit tests, and use mock implementations of the data store interfaces. Data (DAO) tests[2] are generally run across every implementation using only the public interface. This helps me stay sane with the mock implementations. The API tests[3] are integration tests, and use Go's excellent httptest package to boot a real server and execute real HTTP commands. [1] https://github.com/keratin/authn-server/tree/master/services https://github.com/keratin/authn-server/tree/master/services [2] https://github.com/keratin/authn-server/tree/master/data https://github.com/keratin/authn-server/tree/master/data [3] https://github.com/keratin/authn-server/tree/master/api/accounts https://github.com/keratin/authn-server/tree/master/api/acco...
Lord_Zero 9y ago
Check the make file: https://github.com/keratin/authn-server/blob/master/Makefile#L51 https://github.com/keratin/authn-server/blob/master/Makefile... Notice it runs "go test $(shell glide nv)" `glide nv` is a command that gets you all packages except the vendor directory https://github.com/Masterminds/glide#glide-novendor-aliased-to-nv https://github.com/Masterminds/glide#glide-novendor-aliased-... then read the go doc for test https://golang.org/cmd/go/#hdr-Test_packages https://golang.org/cmd/go/#hdr-Test_packages: > 'Go test' recompiles each package along with any files with names matching the file pattern "*_test.go".
plexicle 9y ago
Yeah, you missed them.

brianolson 9y ago

It's just name/pass It would be much more interesting to me if it also did Oauth2 login with Google/Facebook/Twitter/etc.

cainlevy 9y ago
Yeah, name/pass sounds pretty simple, doesn't it? But doing it correctly, securely, with a service architecture? That gets interesting. > It would be much more interesting to me if it also did Oauth2 login with Google/Facebook/Twitter/etc. Totally agreed. The reason I designed AuthN around accounts first is because I believe that's the best way to launch an app. OAuth2 and OIC logins are powerful, but they're secondary to the classic login.

ahoka 9y ago

"Microservices perform better, especially when written in Go." Nonsense.

ShabbosGoy 9y ago
Sort of agree, that's a very noisy and broad statement. I'd argue that the underlying I/O and event loop implementation matters more. At the end of the day it's all about highly available systems. Am I wrong?
- ahoka 9y ago
  You are right. Architecture is all that matters unless you are in some very special niche.
- andrewstuart2 9y ago
  Microservices need to be divided up very carefully, with full knowledge of the latency trade-off of moving functionality across a network gap. A same-datacenter round-trip takes 5,000 times longer than a main memory access, and 1,000,000 times longer than an L1 cache access. There's no silver bullet in performance or scalability. Each solution will require trading off advantages that matter less to achieve business goals. Here are a few references that leap to mind (I keep the first printed out and pinned right next to my monitor). https://gist.github.com/jboner/2841832 https://gist.github.com/jboner/2841832 https://www.quora.com/What-are-some-mind-blowing-facts-about-computers/answer/Thomas-Cormen-1 https://www.quora.com/What-are-some-mind-blowing-facts-about...
  - sealthedeal 9y ago
    The latency you speak of is not noticeable to an end user, unless that end user is an HFT client. Great reference though.
  - mentat 9y ago
    The gain is decoupling deploy and implementation, not latency performance (or network reliability).

kuschku 9y ago

Am I missing something, or does this really have no support for TOTP/HOTP? An authentication system without 2FA or U2F support in 2017 seems... lacking (or unfinished).

cainlevy 9y ago
It's on my roadmap. Prioritizing is hard. :/

nmenglund 9y ago

How does AuthN compare to Keycloak? http://www.keycloak.org http://www.keycloak.org

cainlevy 9y ago
Keycloak does some really great things. It does require managing a Java runtime though, and is missing the streamlining that allows AuthN to run as an invisible API. Keycloak (and similar) hosts and renders your login page. You customize through theming. You're expected to redirect users through a standard OAuth2/OIDC flow on a different domain. AuthN doesn't render any HTML. That's all you, from start to finish. This means you have control over the UX and can build the login page directly into your own app, just like you would when using an auth library in a typical monolith.
- guywhocodes 9y ago
  What, I can't simply post to any login/register/logout uri's and expect either a redirect with configuring headers back or an object that let's me manage the token manually? EDIT: I've been trying out keycloak and it looks great but I've always assumed I just had not figured out how to make that happen. As the documentation is quite large and of the harder kind.
- artpar 9y ago
  You can design the login/register page in keycloak completely. From scratch. I have used it before and had done that.

cortesi 9y ago

This looks pretty reasonable! I would love to see a Cloud Storage backend. A minor quibble is that I think that managing your own metrics in Redis is probably not the simplest or most flexible approach - instead, you should consider exposing a /metrics endpoint that can be ingested by the user's monitoring tool of choice (Prometheus/InfluxDB/etc).

cainlevy 9y ago
Thanks! Have you seen the /stats endpoint? It exposes the metrics as JSON, which may be a good match for your suggestion. I'd also like to export the key events to a STATSD-compatible sink so a sophisticated user can manage metrics in their own system. Redis is already on hand because of other features though, and HLL is a pretty cheap integration. I figure it's a decent starting point for many people.
- cortesi 9y ago
  It looks like the /stats endpoint consults the Redis database and returns processed data. If we're aggregating metrics externally, it would be more idiomatic for this to be totally stateless and just expose hot metrics - it's the aggregator's job to store and process the data. This can be quite painless using something like the Go Prometheus library. Being tied to Redis is also not great. For instance, it looks like everything apart from the metrics could comfortably live in Google Cloud Storage if you had a backend for it. Cloud Storage really isn't an appropriate place to put frequently updated counters, though. So if I deployed AuthN, I would want to be able to ditch Redis. I should stress, though, that these are quibbles. I think AuthN looks very nice, and the quibbles are cropping up because I'm trying to figure out if I can use it. :)
  - cainlevy 9y ago
    That all sounds like a direction I'd happily consider: * Google Cloud Storage implementations for data interfaces * Metrics interface with a Prometheus implementation (STATSD to follow) * Redis-backed HLL metrics are optional Feel free to open issues in the tracker if you reach that point!

tetraodonpuffer 9y ago

the toplevel links (implementation / deployment / configuration) don't work for me, they go to say /keratin/authn-server/docs/config.md which is a 404 presumably instead of /keratin/authn-server/blob/master/docs/config.md

cainlevy 9y ago
Fixed, thanks!
- tetraodonpuffer 9y ago
  no problem, btw, the first time I did make test I got this, but after that I was not able to repro it again and make test always worked, pasting here in case you are interested Creating authnserver_server_1 ... done TEST_REDIS_URL=redis://127.0.0.1:8701/12 \ TEST_MYSQL_URL=mysql://root@127.0.0.1:8702/authnservertest \ go test ./data/... ./models/... ./tokens/... ./ops/... ./config/... ./lib/... ./api/... ./services/... . [mysql] 2017/11/08 13:27:23 packets.go:33: unexpected EOF [mysql] 2017/11/08 13:27:23 packets.go:33: unexpected EOF [mysql] 2017/11/08 13:27:23 packets.go:33: unexpected EOF --- FAIL: TestAccountStore (0.01s) --- FAIL: TestAccountStore/MySQL (0.00s) Error Trace: account_store_test.go:43 Error: Received unexpected error driver: bad connection Connect github.com/keratin/authn-server/data/mysql.ensureDB /home/luser/go/external/src/github.com/keratin/authn-server/data/mysql/db.go:71 github.com/keratin/authn-server/data/mysql.TestDB /home/luser/go/external/src/github.com/keratin/authn-server/data/mysql/db.go:27 github.com/keratin/authn-server/data_test.TestAccountStore.func3 /home/luser/go/external/src/github.com/keratin/authn-server/data/account_store_test.go:42 testing.tRunner /usr/local/stow/go-1.9.0/go/src/testing/testing.go:746 runtime.goexit /usr/local/stow/go-1.9.0/go/src/runtime/asm_amd64.s:2337 ensureDB github.com/keratin/authn-server/data/mysql.TestDB /home/luser/go/external/src/github.com/keratin/authn-server/data/mysql/db.go:29 github.com/keratin/authn-server/data_test.TestAccountStore.func3 /home/luser/go/external/src/github.com/keratin/authn-server/data/account_store_test.go:42 testing.tRunner /usr/local/stow/go-1.9.0/go/src/testing/testing.go:746 runtime.goexit /usr/local/stow/go-1.9.0/go/src/runtime/asm_amd64.s:2337 FAIL FAIL github.com/keratin/authn-server/data 0.040s ? github.com/keratin/authn-server/data/mock [no test files] ? github.com/keratin/authn-server/data/mysql [no test files] ok github.com/keratin/authn-server/data/redis 0.771s ? github.com/keratin/authn-server/data/sqlite3 [no test files]

xena 9y ago

Is there an API client for this in Go?

cainlevy 9y ago
Seems like an oversight, doesn't it? I've created an issue to track here: https://github.com/keratin/authn-server/issues/15 https://github.com/keratin/authn-server/issues/15