Added customUrlValidation

CHANGELOG.md

@@ -1,16 +1,8 @@
 # Change Log
 
-## New Features in Version 4.0.0
+## Lates features
 
-See [Release Notes](https://github.com/manfredsteyer/angular-oauth2-oidc/releases/tag/4.0.0)
-
-## New Features in Version 3.1
-
-See [Release Notes](https://github.com/manfredsteyer/angular-oauth2-oidc/releases/tag/3.1)
-
-## New Features in Version 3.0
-
-See [Release Notes](https://github.com/manfredsteyer/angular-oauth2-oidc/releases/tag/3.0.1)
+See [Release Notes](https://github.com/manfredsteyer/angular-oauth2-oidc/releases)
 
 ## New Features in Version 2.1
 - New Config API (the original one is still supported)

LICENSE

@@ -0,0 +1,7 @@
+Copyright (c) 2017 Manfred Steyer
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

README.md

@@ -7,7 +7,7 @@ Support for OAuth 2 and OpenId Connect (OIDC) in Angular.
 ## Credits
 
 - [generator-angular2-library](https://github.com/jvandemo/generator-angular2-library) for scaffolding an Angular library
-- [jsrasign](https://kjur.github.io/jsrsasign/) for validating token signature and for hashing
+- [jsrasign](https://kjur.github.io/jsrsasign/) until version 5: For validating token signature and for hashing; beginning with version 6, we are using browser APIs to minimize our bundle size
 - [Identity Server](https://github.com/identityserver) (used for testing with an .NET/.NET Core Backend)
 - [Keycloak (Redhat)](http://www.keycloak.org/) for testing with Java
 
@@ -21,24 +21,26 @@ https://manfredsteyer.github.io/angular-oauth2-oidc/docs
 
 ## Tested Environment
 
-Successfully tested with **Angular 6** and its Router, PathLocationStrategy as well as HashLocationStrategy and CommonJS-Bundling via webpack. At server side we've used IdentityServer (.NET/ .NET Core) and Redhat's Keycloak (Java).
+Successfully tested with **Angular 7** and its Router, PathLocationStrategy as well as HashLocationStrategy and CommonJS-Bundling via webpack. At server side we've used IdentityServer (.NET/ .NET Core) and Redhat's Keycloak (Java).
+
+**Angular 6**: Use Version 4.x of this library. Version 4.x was tested with Angular 6. You can also try the newer version 5.x of this library which has a much smaller bundle size.
 
 **Angular 5.x or 4.3**: If you need support for Angular < 6 (4.3 to 5.x) you can download the former version 3.1.4 (npm i angular-oauth2-oidc@^3 --save).
 
 ## Release Cycle
 
-- One major release for each Angular version
+- We plan one major release for each Angular version
     - Will contain new features
     - Will contain bug fixes and PRs
-- Critical Bugfixes on a regular basis
+- Critical Bugfixes on demand
 
 ## Contributions
 - Feel free to file pull requests
 - The closed issues contain some ideas for PRs and enhancements (see labels)
 
 # Features 
-- Logging in via OAuth2 and OpenId Connect (OIDC) Implicit Flow (where user is redirected to Identity Provider)
-- "Logging in" via Password Flow (where user enters their password into the client)
+- Logging in via OAuth2 and OpenId Connect (OIDC) Implicit Flow (where a user is redirected to Identity Provider)
+- "Logging in" via Password Flow (where a user enters their password into the client)
 - Token Refresh for Password Flow by using a Refresh Token
 - Automatically refreshing a token when/some time before it expires
 - Querying Userinfo Endpoint
@@ -71,27 +73,27 @@ npm i angular-oauth2-oidc --save
 ## Importing the NgModule
 
 ```TypeScript
+import { HttpClientModule } from '@angular/common/http';
 import { OAuthModule } from 'angular-oauth2-oidc';
-[...]
+// etc.
 
 @NgModule({
   imports: [ 
-    [...]
-    HttpModule,
+    // etc.
+    HttpClientModule,
     OAuthModule.forRoot()
   ],
   declarations: [
     AppComponent,
     HomeComponent,
-    [...]
+    // etc.
   ],
   bootstrap: [
     AppComponent 
   ]
 })
 export class AppModule {
 }
-
 ``` 
 
 ## Configuring for Implicit Flow
@@ -100,7 +102,7 @@ This section shows how to implement login leveraging implicit flow. This is the
 Single Page Application. It sends the user to the Identity Provider's login page. After logging in, the SPA gets tokens.
 This also allows for single sign on as well as single sign off.
 
-To configure the library the following sample uses the new configuration API introduced with Version 2.1.
+To configure the library, the following sample uses the new configuration API introduced with Version 2.1.
 Hence, the original API is still supported.
 
 ```TypeScript
@@ -229,7 +231,7 @@ var headers = new HttpHeaders({
 });
 ```
 
-Since 3.1 you can also automate this task by switching ``sendAccessToken`` on and by setting ``allowedUrls`` to an array with prefixes for the respective urls. Use lower case for the prefixes.
+Since 3.1 you can also automate this task by switching ``sendAccessToken`` on and by setting ``allowedUrls`` to an array with prefixes for the respective URLs. Use lower case for the prefixes.
 
 ```TypeScript
 OAuthModule.forRoot({
@@ -250,10 +252,11 @@ See the [documentation](https://manfredsteyer.github.io/angular-oauth2-oidc/docs
 
 ## Tutorials
 
+* [Tutorial with Demo Servers available online](https://www.softwarearchitekt.at/post/2016/07/03/authentication-in-angular-2-with-oauth2-oidc-and-guards-for-the-newest-new-router-english-version.aspx)
 * [Angular Authentication with OpenID Connect and Okta in 20 Minutes](https://developer.okta.com/blog/2017/04/17/angular-authentication-with-oidc)
 * [Add Authentication to Your Angular PWA](https://developer.okta.com/blog/2017/06/13/add-authentication-angular-pwa)
 * [Build an Ionic App with User Authentication](https://developer.okta.com/blog/2017/08/22/build-an-ionic-app-with-user-authentication)
-
+* [On-Site Workshops](https://www.softwarearchitekt.at)
 
 
 

docs-src/session-checks.md

@@ -33,7 +33,7 @@ export const authConfig: AuthConfig = {
 To get notified, you can hook up for the event ``session_terminated``:
 
 ```TypeScript
-this.oauthService.events.filter(e => e.type === 'session_terminated').subscribe(e => {
-console.debug('Your session has been terminated!');
+this.oauthService.events.pipe(filter(e => e.type === 'session_terminated')).subscribe(e => {
+  console.debug('Your session has been terminated!');
 })
-```
+```

docs-src/silent-refresh.md

@@ -70,7 +70,7 @@ this
     .catch(err => console.error('refresh error', err));
 ```
 
-When there is an error in the iframe that prevents the communication with the main application, silentRefresh will give you a timeout. To configure the timespan for this, you can set the property ``siletRefreshTimeout`` (msec). The default value is 20.000 (20 seconds).
+When there is an error in the iframe that prevents the communication with the main application, silentRefresh will give you a timeout. To configure the timespan for this, you can set the property ``silentRefreshTimeout`` (msec). The default value is 20.000 (20 seconds).
 
 ### Automatically refreshing a token when/ before it expires
 

docs/additional-documentation/refreshing-a-token-(silent-refresh).html

@@ -655,7 +655,7 @@ <h1 id="refreshing-a-token-when-using-implicit-flow-silent-refresh-">Refreshing
     .oauthService
     .silentRefresh()
     .then(info =&gt; console.debug(&#39;refresh ok&#39;, info))
-    .catch(err =&gt; console.error(&#39;refresh error&#39;, err));</code></pre><p>When there is an error in the iframe that prevents the communication with the main application, silentRefresh will give you a timeout. To configure the timespan for this, you can set the property <code>siletRefreshTimeout</code> (msec). The default value is 20.000 (20 seconds).</p>
+    .catch(err =&gt; console.error(&#39;refresh error&#39;, err));</code></pre><p>When there is an error in the iframe that prevents the communication with the main application, silentRefresh will give you a timeout. To configure the timespan for this, you can set the property <code>silentRefreshTimeout</code> (msec). The default value is 20.000 (20 seconds).</p>
 <h3 id="automatically-refreshing-a-token-when-before-it-expires">Automatically refreshing a token when/ before it expires</h3>
 <p>To automatically refresh a token when/ some time before it expires, just call the following method after configuring the OAuthService:</p>
 <pre class="line-numbers"><code class="language-TypeScript">this.oauthService.setupAutomaticSilentRefresh();</code></pre><p>By default, this event is fired after 75% of the token&#39;s life time is over. You can adjust this factor by setting the property <code>timeoutFactor</code> to a value between 0 and 1. For instance, 0.5 means, that the event is fired after half of the life time is over and 0.33 triggers the event after a third.</p>