Giter Site home page Giter Site logo

docs's Introduction

Auth0 Documentation

This repository contains the Auth0 Quickstarts, but most other documentation content in this repository is no longer up to date, and is not the source of content at https://auth0.com/docs. Pull requests and issues for Quickstarts can still be submitted here, but most other content is no longer hosted on GitHub and therefore no longer open-source. If you are an Auth0 employee trying to make a change to other documentation, please submit a ticket or contact the Documentation Team to request access to our content management system.

Please review the Contributing Guidelines before sending a PR or opening an issue.

  • If you are looking for the application that hosts the Docs content, see auth0-docs.
  • If you would like to modify the Management API v2 API docs, they are generated from the api2 repository.

Both of the above repositories require team access.

Editing Docs Content

Auth0 Docs are no longer maintained in this Github repository. Employees can request access to our content management system to update Docs directly. Outside contributors can submit requests under the Issues section in this repository.

Editing Quickstart Content

  • You can edit the Quickstarts by using the GitHub web editor and editing a file. This is best suited for typos and small changes.
  • You can also pull down the /docs repo to your computer via Git and edit files in your local editor before pushing a new branch (or a branch to your own fork of the project). You can then go to GitHub.com and start a PR. We will be able to review the changes in a Heroku test application prior to merging.
  • Lastly, you can run and test the docs site locally (access available to Auth0 employees only). This option is best suited for repeat contributors or for complex contributions. You gain the benefit of locally testing and viewing your changed or added pages, navigation, and config, but you also gain the complexity of dealing with the local docs app, setting it up, and keeping it updated.

Regardless of which option you use, please review any relevant sections of the Contributing Guidelines before sending a PR.

Issue Reporting

If you find a bug or inaccuracy in the documentation content, please report it in this repository's issues section. Please do not report security vulnerabilities on the public GitHub issue tracker. The Responsible Disclosure Program details the procedure for disclosing security issues.

Author

Auth0

License

This project is licensed under the MIT license. See the LICENSE file for more info.

docs's People

Contributors

aaguiarz avatar alexisluque avatar angelalazar avatar annyv2 avatar avanscoy avatar awie3di avatar catografix avatar chenkie avatar cocojoe avatar davidpatrick avatar erjohnson avatar eugeniop avatar hzalaz avatar jeffreylees avatar jerriep avatar jfromaniello avatar joshcanhelp avatar lbalmaceda avatar lobo avatar mgonto avatar mpaktiti avatar nicosabena avatar ntotten avatar petergfernandez avatar rkhoriander avatar sandrinodimattia avatar siacomuzzi avatar tamigoodall avatar vmartynets avatar woloski avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

docs's Issues

Classic ASP Tutorial - Server Error 500

In the tutorial referred https://auth0.com/docs/quickstart/webapp/asp-classic when you complete the steps of it, the developer might find with a Server Error 500 (The test was made on IIS7 over windows 7) Actually, the code works as intended, it retrieves the user info but it has no redirection after it finishes, so, in the particular case of this test, it throws a 500 server error. HTML code can be added to the callback code, in that way the example will work seamlessly.

AngularJS Tutorial - cdn reference outdated

AngularJS reference link: https://auth0.com/docs/quickstart/spa/angularjs/no-api

The reference indicated above in the tutorial is different from the reference at the bottom of step/subtitle 3, that asks to change the cdn reference. See image below.
image

Also needed is to check the second reference (in the line with the text "For more details...", also shown in image). The current auth0.js reference is: http://cdn.auth0.com/w2/auth0-6.js, as obtained from here

Auth0 + NodeJS API Seed - README.md has outdated instructions

If you review the README.md file created with the Auth0 + NodeJS API Seed project you will notice that there are two issues:

  • does not specify the required command npm install
  • it asks the user to create the .env file and do a configuration that already exists in the project files.

Please see the attached image.

image

Javier
(in behalf of TechAID)

NET API seed project lacks simple reference to its Cors implementation (dependencies)

Link to the related tutorial: https://auth0.com/docs/quickstart/spa/javascript/aspnetweb-api
The NET API seed project needs a simpler, more explicit indication to its referenced Cors implementation.
Although the tutorial references to an external webpage for configuring CORS, the seed-project includes a code implementation for CORS, although the dependency cannot be obtained out-of-the-box.
There should also be a reference to the command: Install-Package Microsoft.AspNet.WebApi.Cors

Image follows below:
image

Missing docs for "Improved brute force protection"

Right now, there is no info about this topic.

To answer the questions:

  • how does it work?
  • what is the impact to the user whose "account" is trying to be breached?

Auth0 implements algorithms to detect suspicious login attempts. When a suspicious activity is detected, Auth0 will block subsequent login attempts originating from the same computer. It will also send an email to the user notifying him containing link to re-enable the origin of the request. Notice that Auth0 never blocks the user itself, just the attempts from the suspicious origin.

  • are all access from a suspicious ip blocked or is it the combination of username/ip that is blocked?

It depends on the algorithm and might change based on the context and evolution of the algorithm

This is an example of the email that is sent to the user

Blocked Access Attempt

We detected suspicious activity from the ip: 190.18.158.85 from Buenos Aires, Argentina.

If that is your IP address click here to unblock it. Otherwise disregard this email.

Clarification: Your account is not blocked, only access to it from the aforementioned IP.


Thanks, 
Default App

It can be edited in the dashboad under Emails -> templates -> Blocked Account Email We need to change the tempate name to other than Blocked Account, maybe Blocked Login Attempt?

Auth0.WindowsPhone package not working with .Net Framework v4.5

Installing NuGet Package for Windows Phone fails on .Net Framework 4.5 application:

PM> Install-Package Auth0.WindowsPhone
Installing 'Auth0.WindowsPhone 1.4.1'.
Successfully installed 'Auth0.WindowsPhone 1.4.1'.
Adding 'Auth0.WindowsPhone 1.4.1' to WebApplication2.
Uninstalling 'Auth0.WindowsPhone 1.4.1'.
Successfully uninstalled 'Auth0.WindowsPhone 1.4.1'.
Install failed. Rolling back...
Install-Package : Could not install package 'Auth0.WindowsPhone 1.4.1'. You are trying to install this package into a project that targets '.NETFramework,Version=v4.5', but the package
does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author.
At line:1 char:1

  • Install-Package Auth0.WindowsPhone
  • - CategoryInfo          : NotSpecified: (:) [Install-Package], InvalidOperationException
    - FullyQualifiedErrorId : NuGetCmdletUnhandledException,NuGet.PowerShell.Commands.InstallPackageCommand
    

Vanilla JS + NET API - Missing detailed and accurate information for binding API to front end

Links to tutorial: https://auth0.com/docs/quickstart/spa/javascript/aspnetweb-api

The information to bind the api from the front end is not present in the tutorial.
Tutorial will be greatly enhanced with some basic information about accurately binding vanilla js front end with NET API seed project, instead of having the developer investigate too many web references on the subject.
No suggestions developed yet.

React seed project throws a 401 unauthorized error out of the box

Auth0 tutorial React reference: https://auth0.com/docs/quickstart/spa/react/no-api

After downloading and serving the React seed project (no api), the app throws a 401 unauthorized error.

react-load-error

I tried hard-coding the token parameters (auth0 clientId & auth0 domain) as per the instructions in the tutorial, but received the same error.

UPDATE: Problem resolved.
Ensure to use a port different than 3000 when serving the seed project, May be needed updating the instructions in the project's readme file.

AngularJS code snippet needs tweaking for a more practical usage

Auth tutorial reference link: https://auth0.com/docs/quickstart/spa/angular/no-api

In the page, subtitle "Step 3 Let's implement the login" presents code in the form of a function, which is not ready to be copied into a new controller file. (See attached image Login-code-snippet.png)

Below is the suggestion

angular.module('YOUR-APP-NAME').controller('LoginCtrl', ['$scope', '$http', 'auth', 'store', '$location', function ($scope, $http, auth, store, $location) {
  $scope.login = function () {
    auth.signin({}, function (profile, token) {
    // Success callback
      store.set('profile', profile);
      store.set('token', token);
      $location.path('/');
    }, function () {
    // Error callback
    });
  }
}]);

Unclear instruction in Node.JS server platform tutorial - Step 2

In https://auth0.com/docs/server-platforms/nodejs in the step 2 the tutorial states:
2. Configure passport-auth0 and shows a code with the data from the account logged in.

step2

Some developers could get this as if there is a file named passport-auth0 which needs to be setup in order to continue, actually, that file is the implementation of methods abstracly defined in the node_modules installed with the npm command and the file must be created.

One can notice that on the step 3 in the code comments but it would be better to directly state that the file must be created.

step3

Phonegap Native Tutorial - key information missing

In the following tutorial https://auth0.com/docs/quickstart/native-mobile/phonegap/no-api
on step 1 you tell the developer that if they are using phonegap build service they should add the plugin using... actually they have to add an entry to the config.xml as it is described here http://docs.build.phonegap.com/en_US/configuring_plugins.md.html it could be more specific detailing the entry has to be added to the config.xml file and giving an example or referencing the phonegap documentation.
plugin

Xamarin tutorial shows outdated images

Image shown on step 3 of Xamarin tutorial (No API) is from an outdated version of the Login Widget. New version has "Lock" logo.

2015-06-06_1505

Newer version of login widget (Lock)
2015-06-06_1509

VanillaJS - NET API seed project - missing reference to Auth0-ASPNET nuget package

Link to Auth0 tutorial: https://auth0.com/docs/quickstart/spa/javascript/aspnetweb-api

Seed project cannot be launched due to a missing nuget package called Auth0-ASPNET, which is not mentioned in the tutorial.
Without the mentioned package. an exception is raised:

Cannot load assembly System.Web.Http
net-api-exception

Suggested solution is to add a reference to the Auth0-ASPNET package in the tutorial, and alternatively within the seed project itself.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.