[
https://issues.apache.org/jira/browse/WHIMSY-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15951866#comment-15951866
]
Sebb commented on WHIMSY-54:
----------------------------
I suspect the part about the auth credentials can be ignored for now.
However I think it would be worth investigating if the auth handling can be
simplified.
It may be possible to rearrange the installation directories of the code on the
server to allow HTTPD to do the auth.
I think the existing external URLs can then be mapped accordingly so they don't
change.
> Re-organise auth. by TLD?
> -------------------------
>
> Key: WHIMSY-54
> URL: https://issues.apache.org/jira/browse/WHIMSY-54
> Project: Whimsy
> Issue Type: Improvement
> Reporter: Sebb
>
> Various parts of Whimsy require auth.
> At present this is done per app, which results in quite a complicated scheme.
> Also the auth conf is held in puppet whereas the app is in the Whimsy repo,
> so it's tricky to relate them.
> When adding a new app, the puppet config has to be updated as well.
> This can easily be overlooked.
> Maybe we should just use auth at the top level directory?
> This might require some apps to be moved, but would be much simpler to
> maintain going forward.
> The following levels are used currently:
> None
> ASF Committers
> ASF Members and Incubator PMC
> ASF Members and Officers
> ASF Members
> ASF Secretarial Team
> This suggests the following directories as a minimum:
> committers
> incubator
> officers
> members
> secretary
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
