@holdusback What do you mean by "increase so much in such a short amount of time"?
The documentation rly need to be re done on the API imo. To have a refresh token you must the grant type "password", if you use the other one "client_credentials" you have a token which cant be refreshed so its a bit useless, that why I had a lot of token, cause a token expire in 1 hour.
Not familiar with oauth2 so Im still learning, but for now I have a small 100 lines of code which work, I can create a access_token, refresh it if he is expired
Also this helped me so much : https://stackoverflow.com/questions/66301872/suitecrm-api-v8-login-authentication-for-password-grant-not-working
The code from the documentation didnt worked, this one worked
There is also nothing about the refresh token, so Im using this to understand : https://www.oauth.com/oauth2-servers/making-authenticated-requests/refreshing-an-access-token/
2 replies
(no Docs on that yet, but I can help with the basics)
Also there is no indication of the expiration time of the refresh_token, so if the refresh token become expired my entire function will not work, IDK how to deal with this
I found a strange thing, and maybe a security issue. A user with status desactivate (So he cant login ?) can to a forgot password, and receive the mail to reset his password
Is that normal ?
I'm just imagining things, but who knows.
As long as it's not a compromise to security, I would leave it like it is.
Hi, I being writing some tests and sometimes i want the records keep alive. I set the cleanupStrategy to be == 'refresh' and what it tries to do is to truncate all table of my database. I do not want to do that, I will want to specify which table needs to be truncated or specify which records must be deleted at tearDown() method. Did u do something like that?
Modern Authentication enabled?
They are in the database but deleted from the entry detail view... got to rollback on my production env
All email adresse are back
Idk if it will pump someone cuz the issu is closed but look like this bug is still active : salesagility/SuiteCRM#4958
Hi @holdusback , probably same as this one: salesagility/SuiteCRM#8989. I believe @JanSiero was working in a proposal, but it seems more complicated than expected
Hi @holdusback , probably same as this one: salesagility/SuiteCRM#8989. I believe @JanSiero was working in a proposal, but it seems more complicated than expected
Yup, look like you are right, hope someone can fix this... IDK if its still not fixed in 8.0+ tho
Has anyone else ever noticed that if you merge two duplicate records that the "Date Created" doesn't always end up as the oldest of the two "date_created" values? I feel like this is a bug, but wanted to get feedback to see if other people feel this is beneficial. If so, shouldn't the value be shown on the merge screen so you can at least see which value it's going to be come?
Welcome back Frank!
Since the lifetime is 24h I have a new line every day, so the list is growing and never purged
Hi @gunnicom, nice to see that you're back! If you want to be more active, consider to join the Community Working Group:
https://community.suitecrm.com/t/suitecrm-community-working-group-invitation/83578
https://community.suitecrm.com/t/suitecrm-community-working-group-invitation/83578
This is huge, finally !
I agree that PRs are not getting much love (and that is a problem that terribly complicates developing anything for SuiteCRM), but I do see this one as different. SalesAgility are focused on v8, which is understandable, and this is quite a critical step, and one that absolutely cannot be done without the Community: the migration script has to be tested "out there" on the real-world installations. So it surely will be getting attention (I think).