• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

jjbohn / omniauth-openid-connect / 47 / 4
99%
master: 99%

Build:
DEFAULT BRANCH: master
Ran 15 Mar 2014 11:47PM UTC
Files 4
Run time –
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

15 Mar 2014 11:44PM UTC coverage: 100.0% (+5.1%) from 94.898%
jruby

push

travis-ci

jjbohn
Use preferred username as the omniauth nickname

There's a difference of opinion on what nickname means between the
OmniAuth Auth Hash Schema and the OpenID Connect spec.

According to the OpenID Connect spec
> Casual name of the End-User that may or may not be the same as the
> given_name. For instance, a nickname value of Mike might be returned
> alongside a given_name value of Michael.

According to OmniAuth:
> The username of an authenticating user (such as your @-name from
> Twitter or GitHub account name)

98 of 98 relevant lines covered (100.0%)

1.33 hits per line

Source Files on job 47.4 (jruby)
  • Tree
  • List 0
  • Changed 1
  • Source Changed 1
  • Coverage Changed 1
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 47
  • Travis Job 47.4
  • 7d77e9d0 on github
  • Prev Job for jruby on master (#46.4)
  • Next Job for jruby on master (#50.4)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc