Security issue
See original GitHub issueHi @gabifiolek , Please check the security option.
The error occurs when using the filestack_field tag with security option.
Of course I’ve already set in the application.rb file app_secret
and security
options.
Just got this error
undefined method `policy' for {"call"=>["pick", "read", "store", "convert", "remove"]}:Hash
Please check for this issue.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:15 (6 by maintainers)
Top Results From Across the Web
Security Issues report - Search Console Help - Google Support
The Security Issues report lists indications that your site was hacked, or behavior on your site that could potentially harm a visitor or...
Read more >Security issue definition and meaning - Collins Dictionary
Security issue definition: An issue is an important subject that people are arguing about or discussing . | Meaning, pronunciation, translations and ...
Read more >10 Common Web Security Vulnerabilities - Toptal
Don't suffer through a security breach—take action before any problems arise. Master these 10 common web security vulnerabilities now.
Read more >Configuring issue-level security - Atlassian Documentation
Issue security levels are created within issue security schemes and let you control which user or group of users can view an issue....
Read more >Topic A: Security issues on the Internet - BC Open Textbooks
Security Issues · Hacker · Malware · Computer virus · Trojan horse · Worm · Phishing · Spyware.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’ve used filestack-rails 5.2.2 and did not set the version in the configuration file.
@joaopedre Many months ago I changed it because some of our clients requested to generate security per request. The security stopped working for him just in 1 hour after deployment. Policy and signature key pair was generated once, in initializers in Rails application. When the server started, it did not change in next requests.
That’s why this change broke your code, because I moved the security generation to application_helper. I’ll figure it out how to handle both cases asap.