The bot automatically closes it, if there's no activity from the ticket owner. @kirotech, I reopened the ticket. and please send an email to info@abp.io if you have such issues. Many people are subscribed to this topic and reading your -personal- problem.
Hey I don't think this problem just for us. I would suggest you to keep tickets open for at least 30 days. Because not everybody has time to respond with technical details in 7 days.
Another suggestion I would like to make. We need private tickets. Because paying customers are paying for support also why all tickets has to be public? Some problems are delicate and includes security questions like we have with your not working oauth openid functionality we have to share our applications configurations publicly this just doesn't make any sense.
Also another thing. I think your support tickets creator filter is privacy problem. If I search @gmail.com I can find emails from your support system database. Also I can find your customers account names. I would suggest to improve that or just remove it from public.
Also another thing how you can improve you support is by providing reliable information when you going to release bug fixes what we found in your abp commercial. As example your abp commercial payments bugs which we reported and had to ask several times which version fix will be included in.
To ask questions privately, you can upgrade to the Enterprise License plan.
I understand your concern about email privacy but that combo box you mention only shows usernames. If the account owner writes his email to the username area then it'll be shown, if he writes his cell phone its shown. if we remove it from there, it's still visible in the question-answer sections. hence this is not a privacy deal.
On the other hand, if you want to see raw and detailed change logs for every release, please check the full change logs document that we recently started to publish https://docs.abp.io/en/commercial/7.1/change-logs/index
We have to pay 10000 for license to get private tickets? Doesn't look like fair offer sorry. Really appreciate your offer, but no thank you
If your user name combo box is fine with you it is 100% fine with me. No worries here. From customer perspective it just looks strange when I search and I find your customers emails and phones. but if there is no problem it is no problem.
I'm not looking for change logs I'm looking for reliable information provided in tickets when bug fix reported going to be released. Do you see the difference?
The bot automatically closes it, if there's no activity from the ticket owner. @kirotech, I reopened the ticket. and please send an email to info@abp.io if you have such issues. Many people are subscribed to this topic and reading your -personal- problem.
Hey I don't think this problem just for us. I would suggest you to keep tickets open for at least 30 days. Because not everybody has time to respond with technical details in 7 days.
Another suggestion I would like to make. We need private tickets. Because paying customers are paying for support also why all tickets has to be public? Some problems are delicate and includes security questions like we have with your not working oauth openid functionality we have to share our applications configurations publicly this just doesn't make any sense.
Also another thing. I think your support tickets creator filter is privacy problem. If I search @gmail.com I can find emails from your support system database. Also I can find your customers account names. I would suggest to improve that or just remove it from public.
Also another thing how you can improve you support is by providing reliable information when you going to release bug fixes what we found in your abp commercial. As example your abp commercial payments bugs which we reported and had to ask several times which version fix will be included in.
Hello mahmut.gundogdu,
Thank you for your message.
In RP we use standard open id process described in your abp commercial .well-known/openid-configuration.
In your abp commercial openiddict application we have three flows enabled: Allow Authorization Code Flow, Allow Implicit Flow, Allow Hybrid Flow.
Please let me know if you need more information.
Why is this ticket closed it is not done yet: https://support.abp.io/QA/Questions/4595/How-to-implement-single-signout-using-abp
hello, any update regarding this abp commercial single logout issue?
Hello mahmut.gundogdu, here (https://support.abp.io/QA/Questions/4229/How-to-implement-single-signout-using-abp) you provided solution for Single logout using your openiddict commercial angular abp implementation. We mean your provided solution for single logout doesn't work. Angular application does not logout in the solution you provided. Please provide working solution. Also refund technical support credits because solution your provided didn't work sorry.
Any update regarding this?
Hello one more question. Do you know which release version this will get in?
https://github.com/abpframework/abp/milestones
As I understand this fix will come with 7.1 release?
You now going to release 7.0.2 sooner?
Thank you very much. Do you know when this fix is available in some stable release?
