Hi Fred,

After some debugging of 403 access denied messages I discovered the Drupal installation used "http://mysite.com/user/1" as the user id to authenticate or get permissions. But as I never created this userID (I assumed the appID and key were sufficient for the authentication) I didn't get through.

Perhaps it is written somewhere, but perhaps to make it more prominent visible that one should first make the Drupal admin account (the full "http://mysite.com/user/1") an user in OSF before starting to configure the Drupal modules. Or is this not the case?

Thanks,
Roen

Comments

roeneman’s picture

roeneman commented
Status: Active » Closed (duplicate)

Closing, provided warning message in patch in: https://www.drupal.org/node/2410901
When endpoint denies access a drupal message will show the issue as mentioned above as possible solution.

But perhaps this issue could also be incorporated in the Library, but that is outside of the scope of this issue I presume.

Hope this helps,
Cheers, Roen

fgiasson’s picture

fgiasson commented

Hi,

Yes, you are right. If you want to know exactly all the things that are required for installing OSF for Drupal manually, you should check the following OSF Installer code that deploy OSF for Drupal:

https://github.com/structureddynamics/Open-Semantic-Framework-Installer/...

Additionally, there is this drush mak file:

https://github.com/structureddynamics/Open-Semantic-Framework-Installer/...

About the patch, like for the other issue, would it be possible to split it such that we got that single patch for this specific issue? Would be much easier to follow :)

Thanks!

Fred

fgiasson’s picture

fgiasson commented
Status: Closed (duplicate) » Needs work
fgiasson’s picture

fgiasson commented
Status: Needs work » Closed (duplicate)