nvandenbossche/salesforce-iam-flows

Node.js application that implements some of the most common SAML and OAuth flows in Salesforce.

salesforce-iam-flows's Issues

Rework EJS files to avoid repetition of buttons, structure.

Replace request npm package with "got"

Adjustments readme running locally

Please add that you have to clone the repository first when running locally

node -r dotenv/config Server.js gave an error:
Error: Cannot find module 'dotenv/config'
Solved it by adjusting the .env file by adding export before all settings and then first run . ./.env after which i started the server with the command : node Server.js

Client Credential flow is missing

Device Flow data flow looks strange

Find a better way of passing along data in the device flow. Now it's passing data from the backend across 5 classes to get to the output.

Make a test with custom OAuth scopes

Implement SASS

Move to a single page application

Single page where nav bar and loaded scripts remains the same.

Broken URL Cloud Sundial

I did notice, on your repo's readme, Lawrences blog URL has a typo so doesn't send you to their site - https://cloundsundial.com/ > https://cloudsundial.com/

(raised by Jonathan Fox)

There are 2 buttons for Prod and Sandbox but this is irrelevant

The mydomain URL is directing to the correct login page, so Production or Sandbox is not really useful.

You need to merge it into a single button and clearly indicate on the page what the configured domain is.

sso-provider parameter is not supported

https://help.salesforce.com/s/articleView?language=en_US&id=release-notes.rn_security_native_sso.htm&release=244&type=5

EJS files are huge with lots of text

Check how to move the text outside of the EJS files, and how we can avoid duplication across the different files.

Add user cases to details of each flow

I am only missing one thing in the details of the flows. In the IAM exam the questions normally start with a use case followed by the question which flow should be used. Is it possible to, next to the malicious actors section, to add a section with use cases for each flow

Update README to include how to run app locally via node

Flow is not visualised except in logs

Make sure we have a visual overview just like https://openidconnect.herokuapp.com/

Make OAuth scope configurable

Should be a configuration in the ENV variables and then used throughout the app.

Error on SOQL query on heroku

It's works locally, but on heroku SOQL query does not work, app crashes and stops.
Steps to reproduce error

1. Fork
2. Download
3. Cert gen
4. Creation of connected app
5. Create app on heroku using CLI - heroku apps:create {name of the app} --region eu
6. Push code to new app - git push heroku master
7. Update Config Vars
8. Open app https://{name of the app}.herokuapp.com/
9. Select flow
10. Click next
11. Click Next
12. Error visible in logs, and app is not responding