fulls1z3 / ngx-auth Goto Github PK

View Code? Open in Web Editor NEW

58.0 6.0 10.0 1.41 MB

Auth0 platform implementation and JWT authentication utility for Angular & Angular Universal

License: MIT License

TypeScript 99.52% JavaScript 0.48%

angular universal auth jwt server-side-rendering authentication security angular2 angular4 aot

ngx-auth's People

Contributors

Stargazers

Watchers

Forkers

juanpmarin n140191 giulioprinaricotti atol-online helpcontrol johnbendi natarajanbala gomcodoctor torrieri mogambo-garje

ngx-auth's Issues

set content type to application/json

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Support request =>
[x ] Feature request
[ ] Documentation issue or request

Hey!

As i see, the authentication is posting the data with 'content-type:text/plain'.
Is there any option to send the post request with content type: application/json?

migrate from Http to HttpClient

Please, change using

import { Http, Response, URLSearchParams } from '@angular/http';

to HttpClient

how to change the parameters

I'm submitting a ... (check one with "x")

[ x] Feature request

this is how I call the api for jwt request.
const url = server + 'oauth/token'; const headers = new Headers(); headers.append('Accept', 'application/json'); const body ="username=${username}&password=${password}&scope[${captchaToken}]&grant_type=password"; const options = new RequestOptions({ headers: headers }); return this.http.post(url, body, options).pipe(....
but now I want to switch to ngx-auth because of getting better performance in universal. but I I get 400 of bad request. I think this is because of different parameters . how I can change parameters.

make use of Google's JS and Material2 style guides

I'm submitting a ... (check one with "x")

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  <!-- Please check the repository for a similar issue or PR before submitting -->
[ ] Support request => <!-- Please check the repository for a similar issue or PR before submitting -->
[x] Feature request
[ ] Documentation issue or request

Current behavior

Expected/desired behavior

public members without prefix & private members with underscore _ prefix
add JSDocs

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

Environment

Angular version: X.Y.Z

Browser:

For Tooling issues:

Node version: XX
Platform:

Others:

make `loader` property public in the auth service

I'm submitting a ... (check one with "x")

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  <!-- Please check the repository for a similar issue or PR before submitting -->
[ ] Support request => <!-- Please check the repository for a similar issue or PR before submitting -->
[x] Feature request
[ ] Documentation issue or request

Current behavior

Expected/desired behavior

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

Environment

Angular version: X.Y.Z

Browser:

For Tooling issues:

Node version: XX
Platform:

Others:

update documentation for Angular Universal

I'm submitting a ... (check one with "x")

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  <!-- Please check the repository for a similar issue or PR before submitting -->
[ ] Support request => <!-- Please check the repository for a similar issue or PR before submitting -->
[ ] Feature request
[x] Documentation issue or request

Current behavior

Expected/desired behavior

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

Environment

Angular version: X.Y.Z

Browser:

For Tooling issues:

Node version: XX
Platform:

Others:

use compodoc to generate project docs

I'm submitting a ... (check one with "x")

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  <!-- Please check the repository for a similar issue or PR before submitting -->
[ ] Support request => <!-- Please check the repository for a similar issue or PR before submitting -->
[x] Feature request
[ ] Documentation issue or request

Current behavior

Expected/desired behavior

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

Environment

Angular version: X.Y.Z

Browser:

For Tooling issues:

Node version: XX
Platform:

Others:

module resolution error during AoT compilation

I'm submitting a ... (check one with "x")

[x] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report  <!-- Please check the repository for a similar issue or PR before submitting -->
[ ] Support request => <!-- Please check the repository for a similar issue or PR before submitting -->
[ ] Feature request
[ ] Documentation issue or request

Current behavior
As described on fulls1z3/ngx-meta#81

Expected/desired behavior
The compilation should succeed on AoT.

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

Environment

Angular version: ALL

Browser:

For Tooling issues:

Node version: XX
Platform:

Others:

undefined token after successful auth

I'm submitting a ... (check one with "x")

[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report  <!-- Please check the repository for a similar issue or PR before submitting -->
[ ] Support request => <!-- Please check the repository for a similar issue or PR before submitting -->
[ ] Feature request
[ ] Documentation issue or request

Current behavior

I wrote codes like the example,

login(){
    const formModel = this.loginForm.value;
    const username = formModel.username as string;
    const password = formModel.password as string;

    this.auth.authenticate(username, password)
      .subscribe( () => {
        if( !this.auth.isAuthenticated ){
          console.log(this.auth.token);
          console.log('invalidate');
        }else{
          this.router.navigate(['/app/landing']);
        }
      });
  }

It did authentication to the server successfully (can be seen in the below pic) but I got !this.auth.isAuthenticated as true and got undefined from console.log(this.auth.token);

Expected/desired behavior

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

Environment

Angular version: 6.0.0

Browser:

For Tooling issues:

Node version: 5.6.0
Platform: Mac

Others:

angular-cli + universal compliance

I'm submitting a ... (check one with "x")

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  <!-- Please check the repository for a similar issue or PR before submitting -->
[ ] Support request => <!-- Please check the repository for a similar issue or PR before submitting -->
[x] Feature request
[ ] Documentation issue or request

Current behavior
@bliitzkrieg explained at fulls1z3/ngx-meta#56

Expected/desired behavior

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

Environment

Angular version: X.Y.Z

Browser:

For Tooling issues:

Node version: XX
Platform:

Others:

support server-platform

I'm submitting a ... (check one with "x")

[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report  <!-- Please check the repository for a similar issue or PR before submitting -->
[ ] Support request => <!-- Please check the repository for a similar issue or PR before submitting -->
[x] Feature request
[ ] Documentation issue or request

Current behavior
ngx-auth fails to run on server-platform.

Expected/desired behavior
An implementation of mock auth service would solve this problem, and make this library universal-compliant.

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

Environment

Angular version: X.Y.Z

Browser:

For Tooling issues:

Node version: XX
Platform:

Others:

expose auth0 instance and more coverage for auth0 API

[ ] Regression
[ ] Bug report 
[ ] Support request
[x] Feature request
[ ] Documentation issue or request

Current behavior
Firstly, big thankyou to @fulls1z3 for this great wrapper library. Works like a charm! However, currently ngx-auth doesn't allow us to use some of the other great auth0 methods that are available on the internal auth0 instance. As an example; passwordless login/signup, programmatic login/signup, checking/renewing the current session.

Expected/desired behavior
I propose that ngx-auth both exposes the internal auth0 instance, plus provide a few extra 'wrapper' methods (e.g. session renewal).

What is the motivation / use case for changing the behavior?
Providing access to the inner auth0 instance means the developer is able to use the auth0 api directly if they need, plus create some of their own functionality if needed.
Creating more wrapper methods means ngx-auth becomes a more feature-rich wrapper, whilst still handling some of the annoying parts for you (e.g. abstracting away the storage of access tokens & id tokens .etc).

fulls1z3 / ngx-auth Goto Github PK

ngx-auth's People

Contributors

Stargazers

Watchers

Forkers

ngx-auth's Issues

Recommend Projects

Recommend Topics

Recommend Org