Issue Report

Build Error for UWPSample

Description

Upon downloading the UWPSample, A build error has occurred regarding the UWPSampel_TemporaryKey.pfx.

Expected behaviour

Successful Build and Run of the sample

Actual behaviour

Build event error:

Certificate could not be opened: UWPSample_TemporaryKey.pfx.
Cannot find the requested object.

Steps to reproduce the problem

Fresh Clone from repo, build/run

Language / Framework Versions

1. C#
2. UWP

Issue Report

If you are reporting a bug, please fill the sections below (if they are applicable), otherwise feel free to delete those that don't apply. Thank you! 🙏🏼

Description

Any recent breaking change ? Impossible to login anymore since a week now.

Expected behaviour

Authentification success

Actual behaviour

When use for the first time, the authentification window is opening successfully. If we create new user or even try to connect with existent username+ password => Authentification window is closing and it's impossible to connect. The window is briefly opening then immediatly closing. Important NOTE : We still can create new account. (screenShot 1)

Steps to reproduce the problem

1. Launch the project for the first time
2. authentification or inscription
3. Fill the different text field
4. Create/Login button
5. Window is closing
6. Click again on "Create/Login"
7. the window is opening then immediatly closing
8. Impossible to connect or to create new user again

Language / Framework Versions

** UWP project C# **

Testing environment

1. Windows 11 Pro

Screenshots

Filling this, you're helping yourself and repo maintainers in solving your issues quicker! Teamwork makes the dreamwork 🤜🏼🤛🏻

Issue Report

If you are reporting a bug, please fill the sections below (if they are applicable), otherwise feel free to delete those that don't apply. Thank you! 🙏🏼

Description

"Forbidden" error when trying to display login screen in UWP sample app

Expected behaviour

Login screen to be displayed

Actual behaviour

The screen does not show and forbidden error is returned

Steps to reproduce the problem

Download sample app, update to Auth0.OidcClient.UWP v3.1.0, run it.
Note that populating the app ms-app uri causes the login screen to display, but it does not return to the app afterwards. When I downgraded to version 2.4.3 returnUri is pre-populated and everything works as expected.

Language / Framework Versions

1. Language used: C#
2. Framework used: Microsoft.NETCore.UniversalWindowsPlatform v6.2.9

Testing environment

1. Operating system: Win10
2. Browser version: N/A

Screenshots

Feel free to insert here any screenshots that you consider helpful in solving your issue.

Filling this, you're helping yourself and repo maintainers in solving your issues quicker! Teamwork makes the dreamwork 🤜🏼🤛🏻

Issue Report
If you are reporting a bug, please fill the sections below (if they are applicable), otherwise feel free to delete those that don't apply. Thank you! 🙏🏼

Description
"Forbidden" error when trying to display login screen in UWP sample app

Expected behaviour
Login screen to be displayed

Actual behaviour
The screen does not show and forbidden error is returned

Steps to reproduce the problem
Download sample app, update to Auth0.OidcClient.UWP v3.1.2, run it.
Note that populating the app ms-app uri causes the login screen to display, but it does not return to the app afterwards. When I downgraded to version 2.4.3 returnUri is pre-populated and everything works as expected.

Language / Framework Versions
Language used: C#
Framework used: Microsoft.NETCore.UniversalWindowsPlatform v6.2.9
Testing environment
Operating system: Win10
Browser version: N/A
Screenshots
Feel free to insert here any screenshots that you consider helpful in solving your issue.

Filling this, you're helping yourself and repo maintainers in solving your issues quicker! Teamwork makes the dreamwork 🤜🏼🤛🏻

(AUTH-4174)
Sample doesn't contain readme.md file.

Hey there our Auth0 Community OSS Collaborators!

👋 Long time no see!

As you may have seen some time ago, we communicated the fact that we are gradually working on improving your developer experience inside any repo in this org!

If you go to the readme file of this repository, in the first section you can see a note that this repo is supported and maintained by Community Developers, not Auth0. Despite the fact that we have limited bandwidth inside Auth0 Community Team and are not able to effectively review issues and PRs you submit, we want to improve your experience here one step at a time! That's why you should keep reading!

🚀 Auth0 Community Job Offers

If you feel like joining us on a mission to make other developers contributions here more comfortable, here are the links you should visit!

• Technical Community Manager
• Open Application

🛠️ Auth0 Community GitHub org - improvements

We're aiming at your successful developer experience in the long term that's why we introduced a few improvements in the meantime and are looking forward to make even more impact!

• We created a getting-started repo so that you can answer any of your questions before contributing to our community OSS repos!
• We added Code of Conduct so that everyone can collaborate in a peaceful and effective way!
• Wondering how to contribute to our repositories?! Got you covered! We added a Contribution Guideline to easily get you started with your commits and PRs!
• Additionally we added License files to every repo!

Think it's all?! Nah! We ain't stoppin here! ✨

• We introduced issues and PRs labels so you can add them to your contributions and other community developers can easily track and choose which ones they would like to help with!
• The last thing we want to let you know about are Auth0 Community Project Boards. Using them we aim at providing better searchability for people with certain language experience looking to solve stuff in their language of choice and not looking for specific PRs / issues!

❤️ Feedback

Let us know what you think! We're super stoked for your feedback! You can share it here or email us at [email protected]. We know there's a long way ahead of us to make this environment friendly and sustainable but we strongly believe that getting aboard together will let us reach the final destination!