|
6 | 6 | <meta name="viewport" content="width=device-width, initial-scale=1.0"> |
7 | 7 |
|
8 | 8 |
|
9 | | - <link rel="canonical" href="https://docs.peeringdb.com/gov/test/"> |
| 9 | + <link rel="canonical" href="https://docs.peeringdb.com/blog/oauth_not_just_for_networks/"> |
10 | 10 | <link rel="shortcut icon" href="../../img/favicon.ico"> |
11 | | - <title>Test - PeeringDB Docs</title> |
| 11 | + <title>OAuth Isn’t Just for Networks - PeeringDB Docs</title> |
12 | 12 | <link href="../../css/bootstrap.min.css" rel="stylesheet"> |
13 | 13 | <link href="../../css/font-awesome.min.css" rel="stylesheet"> |
14 | 14 | <link href="../../css/base.css" rel="stylesheet"> |
|
46 | 46 | <a href="../.." class="nav-link">About</a> |
47 | 47 | </li> |
48 | 48 | <li class="navitem"> |
49 | | - <a href="../" class="nav-link">Governance</a> |
| 49 | + <a href="../../gov/" class="nav-link">Governance</a> |
50 | 50 | </li> |
51 | 51 | <li class="dropdown"> |
52 | 52 | <a href="#" class="nav-link dropdown-toggle" data-toggle="dropdown">Committees & Task Forces <b class="caret"></b></a> |
|
136 | 136 |
|
137 | 137 | <div id="toc-collapse" class="navbar-collapse collapse card bg-secondary"> |
138 | 138 | <ul class="nav flex-column"> |
| 139 | + |
| 140 | + <li class="nav-item" data-level="1"><a href="#oauth-isnt-just-for-networks" class="nav-link">OAuth Isn’t Just for Networks</a> |
| 141 | + <ul class="nav flex-column"> |
| 142 | + </ul> |
| 143 | + </li> |
139 | 144 | </ul> |
140 | 145 | </div> |
141 | 146 | </div></div> |
142 | 147 | <div class="col-md-9" role="main"> |
143 | 148 |
|
144 | | -<p>hi</p></div> |
| 149 | +<h1 id="oauth-isnt-just-for-networks">OAuth Isn’t Just for Networks</h1> |
| 150 | +<p><em>April 16, 2026</em></p> |
| 151 | +<p>PeeringDB has provided an OAuth service for a long time. <a href="/blog/oauth_users/">It’s popular</a> with networks who want to authenticate other networks but don’t want them to have to create a new account. Until recently, OAuth applications could only be created by organizations with a network.</p> |
| 152 | +<p>But now, organizations that don’t run a network can create an OAuth application and get the benefits of authenticating PeeringDB users.</p> |
| 153 | +<p><img alt="Login to bgproutes.io with PeeringDB" src="../images/bgproutes_io_peeringdb_preferred_login.png" /> </p> |
| 154 | +<p>We made this change based on a request from Thomas Holterbach and the <a href="http://bgproutes.io">bgproutes.io</a> project. This is a project that collects and analyses BGP data. They need to authenticate the connection between the network and the data but don’t need a unique ASN for their service.</p> |
| 155 | +<p><em>“We run a BGP data collection platform and rely on PeeringDB’s strong authentication system, combined with its robust mapping between users, organizations, and the networks they operate, to confidently authenticate operators through its OAuth system and determine which ASNs they manage. This is essential for ensuring the integrity of the data we collect and for clearly identifying the source of each feed.</em></p> |
| 156 | +<p><em>For this, we needed a new feature: the ability to use OAuth without being tied to a specific ASN. The PeeringDB Product Committee was very responsive in understanding our use case and adapting the system to support it. It is now working smoothly, and tens of operators have already connected to our platform using their PeeringDB accounts.”</em> - Thomas Holterbach, bgproutes.io </p> |
| 157 | +<p>Initially, they planned to get access to contact data to authenticate users. This was a challenging way for PeeringDB to meet the project’s needs. The Product Committee didn’t want to change the conditions under which contact data is shared and adding an extra permission would have been complicated.</p> |
| 158 | +<p>In the end, we decided to expand the scope of who could create an OAuth application. Each user is aware that they are using PeeringDB’s OAuth when they login with it. And now, organizations without networks in PeeringDB can take advantage of our OAuth service. This could include facility operators or carriers who decide not to run their own L3 network.</p> |
| 159 | +<p>If you have an idea to improve PeeringDB you can share it on our low traffic <a href="https://docs.peeringdb.com/#mailing-lists">mailing lists</a> or create an issue directly on <a href="https://github.com/peeringdb/peeringdb/issues">GitHub</a>. If you find a data quality issue, please let us know at <a href="mailto:support@peeringdb.com">support@peeringdb.com</a>.</p> |
| 160 | +<hr /> |
| 161 | +<p>PeeringDB is a freely available, user-maintained, database of networks, and the go-to location for interconnection data. The database facilitates the global interconnection of networks at Internet Exchange Points (IXPs), data centers, and other interconnection facilities, and is the first stop in making interconnection decisions.</p></div> |
145 | 162 | </div> |
146 | 163 | </div> |
147 | 164 |
|
|
0 commit comments