Chit Khine
where is the place for OktaDomain?
Matt Raible
In the raw Markdown for this post, we use the following syntax:
issuer: ‘https://{yourOktaDomain}/oauth2/default’,
However, there is logic on this page that replaces “{yourOktaDomain}” with the URL of the Okta org that you last logged in to. For example, the above text renders as the following for me.
issuer: 'https://okta.okta.com/oauth2/default’
Hope this helps!
David
Please at this point - Take Your Vue.js Frontend and Auth Flows for a Test Drive, on my browser i get this error > Cannot GET /
Also at the first npm run dev, my browser adds ‘#/’ to the url which becomes http://locahost:8080/#/
Matt Raible
Can you please compare your code to the example on GitHub. SmartSynchronize is a good tool for comparing directories.
Tip: ignore your node_modules directory when comparing.
Chris
Similar to previous comments, I got errors when trying to install sqlite3.
> sqlite3@4.0.0 install ~/my-vue-app/node_modules/sqlite3
> node-pre-gyp install --fallback-to-build
node-pre-gyp ERR! Tried to download(403): https://mapbox-node-binary…
node-pre-gyp ERR! Pre-built binaries not found for sqlite3@4.0.0 and node@12.2.0 (node-v72 ABI, glibc) (falling back to source compile with node-gyp)
The only solution that worked for me was reverting from node 12.2.0 back to an old version of Node from early 2018 (v8.16.0).
Dipanwita Guhathakurta
I’m getting this error even on cloning the github repo : Unhandled rejection Error [ERR_HTTP_HEADERS_SENT]: Cannot set headers after they are sent to the client.
장윤희
hello! though passed a month ago, i think another person still seek the answer anyway so, i reply , that i found the way that this error go away just typing and execute following command on cmd “npm install sqlite3” !^-^
Geo Nicolaidis
Did you find where the error was? I am getting the same one.
Roberto Amorim
Hi, thanks for your tutorial.
After I followed all steps I got the following error when I try to insert a row:
Error: expected audience is required
at verifyAudience (C:\sources\vue\vue-teste\node_modules@okta\jwt-verifier\lib.js:80:11)
at OktaJwtVerifier.verifyAccessToken (C:\sources\vue\vue-teste\node_modules@okta\jwt-verifier\lib.js:148:5)
at process._tickCallback (internal/process/next_tick.js:68:7)
Matt Raible
Hello Roberto,
Did you use the same version of jwt-verifier that’s used in this post? If not, run the following command to fix it.
npm install @okta/jwt-verifier@0.0.11
See our jwt-verifier upgrading guide for more information.
probie
Excellent article, Do you have one for Facebook or Twitter Social network authentication using Okta or Passport strategies. Thank you.
Chris Roberts
@dipanwitaguhathakurta looks like epilogue is no longer maintained and does not support sequelize v4+ … the solution I found was to switch to finale, see: https://github.com/tommyban…
Chris Roberts
@mattraible you may want to update this article and examples
Matt Raible
Thanks Chris. I’ll update this post in the near future.
Matt Raible
@disqus_kdkaX7gis7 This blog post and example have been updated. See the code changes in oktadeveloper/okta-vue-node-example-example#3. Changes to this post can be viewed in oktadeveloper/okta.github.io#3040.
Bukthi
Hi @@mattraible
I’m getting ‘Error: Please install sqlite3 package manually’ after executing ‘node ./src/server’ command. Please help me to solve this
Matt Raible
Hello,
I didn’t need to do this step when I did the tutorial, but other folks have left comments that they did. You might try running npm install sqlite3.
Bukthi
@@mattraible Thanks a lot, it works !
Scot
I fixed this error Using @okta/jwt-verifier": “^1.0.0” by adding the audience (aud) parameter.
In server.js change the line from
oktaJwtVerifier.verifyAccessToken(accessToken)
to
oktaJwtVerifier.verifyAccessToken(accessToken, ‘api://default’)
----- More at ----
“The expected audience passed to verifyAccessToken() is required, and can be either a string (direct match) or an array strings (the actual aud claim in the token must match one of the strings).”
default Lastname
Hai Allyn Becar can I ask how did you fix it? I was on port 8080 and I put 8081 already