SuiteCRM-7.11.23
So I was trying making a custom API and installing Postman and all of that. I am also using a documentation on how to do so and when I was in the “Verify if rewrite module is installed and activated”, the step said:
"I can check and verify this by checking apache2 sugar.conf file and the directory of this file is “/etc/apache2/sites-available”.
But I don’t have the “/apache2/sites-available/” path and also the sugar.conf file.
Did I do something wrong? How do I fix this. Any kind of tip would be very helpful
Can you provide us what documentation you are following. I can’t find any references to sugar.conf on our docs site 
This is the Documentation that I’m reading. Zipped it because the forum doesn’t allow pdfs
JSON API.zip (1.5 MB)
Interesting, I haven’t seen that PDF before. Where did you acquire it?
Unfortunately that isn’t official documentation so I can’t comment on how accurate that is.
I can only point you to the official docs to help out which is more generic perhaps easier to adapt to your own setup.
I found it online. In hindsight, I should’ve just went to the official documentation instead.
Now, I did that and my question now is:
-
How do I get/make the access token,
-
Where can I find the file to change the AllowOverride from None to All?
You can make access tokens by setting up appropriate grant types in the instance. Highlighted the documentation here Available Grant Types :: SuiteCRM Documentation
The second query is dependent on your server set up. This is the assumption that it’s a LAMP stack (Linux/Apache/MySQL/PHP). Quick google can help you navigate where your apache configuration is. I just query “AllowOverride setup”
I’ve managed to resolve the access_token issue. It was an error on my part as I did not enter the correct path to the token. May I ask though, I can’t find the access_token inside the Api folder, is this just normal behavior? Is it actually not a file as I presumed?
As for my AllowOverride question, I managed to finish the official documentation even without altering it. Also, I am using a VM and CentOS. I managed to find where this file is. I was relying so much on the forum that I forgot to even try to google.
Godspeed to as always samus!
An access token is actually a generated value that acts like a session so yeah it’s not a file. You can have multiple access_tokens for people as long as when you sending a request you have the correct person + access token (generated by whatever authentication type you agreed to use).
No worries. I always remember a saying from my university lecturers… it’s not what you know but how to find it. 
1 Like