New version update: No extra deployment setup is required anymore!

[spencerwooo]

Finally, I managed to land this before 2022. Happy new year! 🥳

TL;DR

For this update, you don't have to create your own client id, client secret, access token, refresh token what-so-ever. The OAuth process is built directly into the project. Tokens are stored with Redis, and refreshed regularly. No more environment variable over the limit issues!

Thought process and migration guides

The catch: you need a Redis connection. A url is sufficient, which you would be storing inside Vercel environment variable as REDIS_URL. You can create one completely for free at https://upstash.com/

As this upgrade brings a persistent storage into the serverless environment, we can further extract configurations and other settings to this storage, instead of config files - even more simplified deployment process, and even - setting UI or admin panels. Something for me to do in 2022 :)

Migration documentations are available at: Migrating from an old project

Auth process screenshots

[opoet]

你好，请问混淆 secret 是啥意思，应该如何填写？

[spencerwooo]

这是获取根目录的时候超时了啊，那是去拿 access token 超时，还是 OneDrive API 那侧超时了？要是本地 npm run dev 还能跑起来的话，看看 log？具体在这里 https://github.com/spencerwooo/onedrive-vercel-index/blob/main/pages/api/index.ts#L24-L65 有 access token 相关的 log 获取输出。

[comicchang]

在本地调试过后，我根据日志提示搞定了……原来是我的REDIS_URL格式不对

原先写的是redis://[email protected]:31183，改成rediss://:[email protected]:31183之后就可以了

谢谢

[sobuj53]

Hello,
I'm also having difficulty understanding how to insert obfuscatedClientSecret. Should I left it blank? If I leave it blank then the token doesn't work. I tried to use this online AES converter https://aesencryption.net/ but no success, I also tried to use bare Client Secret without encryption but this didn't work for me as well. I'm always getting,
AADSTS7000218: The request body must contain the following parameter: 'client_assertion' or 'client_secret'.

Can you please tell me what I'm missing?

PS I've Upstash integration with my vercel account as per the instructions.

[spencerwooo]

@sobuj53 if you are using onedrive international with an admin account (meaning that you can authorise onedrive-vercel-index to access your account), you don't have to customise anything here, keep the client id and obfuscated client secret the same as the main project. the obfuscation is done here if you must use your own client id and secrets: https://github.com/spencerwooo/onedrive-vercel-index/blob/main/utils/oAuthHandler.ts#L9-L13

[sobuj53]

Thank you for your response. I've solved the issue. My account was not accepting the default clientId and obfuscatedClientSecret and was getting same response as 215. However after Obfuscating my generated ClientSecret and encrypting it with onedrive-vercel-index key. I managed to overcome the issue.

[hu3rror]

已经迁移成功。关于 upstash 的 REDIS 的操作，我新建的时候 REDIS 开了 TLS，所以我 environment 中 REDIS_URL需要以 rediss://: 开头，如果连接不成功可以试试。

[tkfanswind]

这个自动生产是自己的client ID吗？需要换成自己的client ID吗？

[spencerwooo]

上面已经提到了。是的，不必替换为原先的自己的 client id 或者 client secret，用项目提供的即可。

[Kasper4649]

用的教育版 OneDrive，没有添加未授权应用的权限，只能自己手动添加 Client Id 和 Secret 🌝

[comicchang]

#215 (reply in thread)

把你的secret用aes加密一下，填到obfuscatedClientSecret里面

[coldpub]

Hello, the third step does not need to change the API, when I click Store tokens, the homepage has been 404

[coldpub]

Oops, that's a four-oh-four.
Request failed with status code 500
Press F12 and open devtools for more details, or seek help at onedrive-vercel-index discussions.

[ChirmyRam]

Oops, that's a four-oh-four. Request failed with status code 500 Press F12 and open devtools for more details, or seek help at onedrive-vercel-index discussions.

你好，请问是怎么解决的呢？

[coldpub]

我就按照流程来的 最后一步需要等会才会生效 然后强制刷新一下就可以了

[ChirmyRam]

我就按照流程来的 最后一步需要等会才会生效 然后强制刷新一下就可以了

找到问题了，我redis url少了个冒号🥴

[coldpub]

ok!

[coldpub]

i ok!

[jhonnyminedr]

Hey guys, I did the new way without replacing given cliend id, obsucuted client secret it says admin permissions needed, can I know how to do with my credentials, why is osucutated client secret (any one with problem of admin permissions needed?) at vercel link

in step 2/3 link i got

& later i replaced cliend id in this photo

got the authorisation code but after it in later step it says

Step 3/3: Get access and refresh tokens

Whoops, looks like we got a problem: invalid_client.

AADSTS7000215: Invalid client secret is provided.
Trace ID: 8ffc91f6-f44b-44ee-a3fb-7cc360c89e01
Correlation ID: 8c777adb-ff8c-4456-bf87-2193e2494870
Timestamp: 2022-01-02 02:16:37Z

Check out Microsoft's official explanation on the error message.

i haven't replaced the obsucated client secret can i know how to replace it..
thanks :)

[spencerwooo]

the obfuscation is done here https://github.com/spencerwooo/onedrive-vercel-index/blob/main/utils/oAuthHandler.ts#L9-L13

basically we use a default aes encryption with a default encryption key onedrive-vercel-index. you can run this function to generate your own encrypted client secret, or use some online tool for this (try googling online aes encryption or something)

[avgnerd]

Is there a way to use it with multiple OneDrive accounts?

[spencerwooo]

maybe, future versions. for now you can deploy multiple instances of the project (but you'll need multiple redis connections, where the free upstash only provides one)

[ChirmyRam]

maybe, future versions. for now you can deploy multiple instances of the project (but you'll need multiple redis connections, where the free upstash only provides one)

There is no need to create multiple accounts, I found that one account in upstash can create multiple teams, each team has a redis connection, I did just that, now I have created six teams, but the maximum number is unknown.