403 during bulk_set_stream call and unable to login

[devtools]

When asking for help in this category, please make sure to provide the following details:

• SDK Version: “@web3auth/base”: “6.1.7”, “@tkey/default”: “^11.0.2”

• Platform: Web

• Browser Console Screenshots:
  

  

• If the issue is related to Custom Authentication, please include the following information (optional):

  • Verifier Name: pay3-tkey-jwt-verifier
  • JWKS Endpoint: https://sw2iudowi5.execute-api.ap-south-1.amazonaws.com/pprod/v1/user-management/.well-known/jwks.json
  • Sample idToken (JWT):

eyJraWQiOiIxYmI5NjA1YzM2ZVRCWkJMOHllMDRmcjBkcEo2OTM4NjgzMDIwMmIyZCIsInR5cCI6IkpXVCIsImFsZyI6IlJTMjU2In0.eyJzdWIiOiJhaml0QHBheTMubW9uZXkiLCJhdWQiOiJ3ZWIzYXV0aCIsImlzcyI6Imh0dHBzOi8vc3cyaXVkb3dpNS5leGVjdXRlLWFwaS5hcC1zb3V0aC0xLmFtYXpvbmF3cy5jb20vcHByb2QvdjEvdXNlci1tYW5hZ2VtZW50Ly53ZWxsLWtub3duL2p3a3MuanNvbiIsImlhdCI6MTcwMzMxOTEyMiwianRpIjoiYWppdEBwYXkzLm1vbmV5IiwiZXhwIjoxNzAzMzIwOTIyfQ.qD9jzkhNllfvsgfbak9sf_c_HevZ5yHaQjwi3_7jBOM8s-37A-SrHk-VN7F2hlAYJpjhOmHaXiWQrPoo2z5r9n8BwDO2eHUbwN6cWYwPbsJpSIE7bBIasOmMhuGIrv5HF3_2Ke6CeuovOEqD6ZOONZBaUYMe5axMCCeCDZttIKa6TeQ1MUayX3WYw0GQNp2b7Mq5LTAvgrcdCNQD0-A7ujtB1B1NZ2LhMbs-cF6-DcADpKHFyepenRtiCtqyWJZUFSsdwm0eurSKJk4xpDqn7Puzx__0d-w4s3RNTvIAor_ut6yoZ0yrhJxsMd7-gLyGtNFpAH2rurdTPxZHeXyd6w

Also, kindly provide the Web3Auth initialization and login code snippet below. This will help us better understand your issue and provide you with the necessary assistance.

      await (this.tKey.modules.securityQuestions).inputShareFromSecurityQuestions(answer);
      await this.storePostboxAndGetPvtKey();
      const newShare = await this.tKey.generateNewShare();
      const shareStore = this.tKey.outputShareStore(newShare.newShareIndex);
      await (this.tKey.modules.webStorage).storeDeviceShare(shareStore);

[devtools]

@web3auth-team Please help us on this issue, many of our clients are unable to login

[cherngwoei]

Hi,
Please try remove the newShare generation ( do not store to device )
It is possible that you have created too much shares.

For suggested implementation,
Only generate new share on request/demand. (eg, backup share, or button to add device share)

• try limit the total shares to less that 10. you can also delete the old device share that is not in used.

[devtools]

Thanks a lot @cherngwoei , we will test with the aforementioned solution and get back to you

[devtools]

Thanks a lot, this solution worked for us @cherngwoei. We are limiting the shares to 3