Fedora 4 uses servlet container authentication (Realms) to provide minimal protection for your repository with a master "superuser" user and password. The superuser credentials are configured in your web application container's properties file; once configured, all management (write) operations will require authentication.
The superuser property name is fedoraAdmin.
This is comparable to the fedoraAdmin superuser role in Fedora 3, used for Fedora 3 API-M operations.
Configure your repo.xml file
Add the beans authenticationProvider and pep to your repo.xml, file, and make the modeshapeRepofactory bean dependent on authenticationProvider. Here is an example repo.xml:
repo.xml with authentication configured<bean name="modeshapeRepofactory" class="org.fcrepo.kernel.spring.ModeShapeRepositoryFactoryBean" p:repositoryConfiguration="${fcrepo.modeshape.configuration:classpath:/config/rest-sessions/repository.json}" depends-on="authenticationProvider"/> <bean name="pep" class="org.fcrepo.auth.roles.basic.BasicRolesPEP"/> <bean name="authenticationProvider" class="org.fcrepo.auth.ServletContainerAuthenticationProvider"> <property name="pep" ref="pep"/> </bean>
Jetty
Fedora4 uses the org.eclipse.jetty.security.HashLoginService
Jetty login service.
See the Jetty Authentication documentation for more details.
Tomcat
Related articles
There is no content with the specified labels