Security in WAS 6.1 - websphere

In WAS 6.1, when I click on Users and Groups --> Manage Users, I get error:
"You must enable administrative security and security must be activated to manage users and groups using the federated repositories feature."
How to go about solving this? I am new to WAS

What you need to do is to enable the administrative security. Typically this involves configuring your server against the file based registry or LDAP.

Related

CAS default user and missing permission to Administrator Panel

I need create fake CAS server on localhost. I copy this repo and I run this. But now I have problem with access to Administration panel or something like that on user: casuser and password: Mellon.
Is there any UI to manage CAS? How can I configure CAS to use this as localhost authentication server?
Is there any UI to manage CAS?
There is a UI that would allow one to manage application registrations and policies with CAS, but as of this writing, there is no UI to manage the CAS configuration itself. The Spring Boot Admin project might be an option to research.
Today, CAS configuration more or less is a source-driven process where you configure modules via build.gradle file and relevant configuration via a cas.properties file. You'll need to edit these by hand to prep your deployment.

SonarQube - SSO only allow specific users access to SonarQube via Security group

I am implementing SSO into our SonarQube. Due to our company having so many users I want to only allow users that are within a specific security group e.g. SonarUsers. To have access to SonarQube and would be associated with a SonarUsers SonarQube Group and the same for SonarAdmins.
How/Is this possible?
Using SonarQube 6.2 and SSO Plugin 1.5.1
From a single-sign-on perspective, your only option would be to have your SSO system refuse to authenticate them. But that's probably not what you want.
On the SonarQube side, since you're delegating authentication your only option would be to refuse them permission to see anything once they've authenticated. Do that by restricting who can Browse your projects

How to create user and password in existing websphere app server

I have already installed Websphere Applcation Server 8.5.5 on my machine without username password.
But for some reason now after using it for several days without any problem, today I got a problem where I am asked to enter username and password in one of the applications which I deployed on WAS8.5.5.
Now how can I create a username and password in an already installed WAS 8.5.5?
If you want to disable application security,
in Security -> Global Security section, uncheck Enable application security
else you want to enable application security, configure User account repository with available realm definitions.

Websphere multiple authentication provider

I am looking for some information about using multiple authentication provider with WebSphere Liberty at the same time. Requirement is to have AD (LDAP) auth as main authentication and for users not allowed to be listed in AD have a simple database for authentication.
Thanks for any hints.
You can implement a custom user registry to meet these requirements:
http://www-01.ibm.com/support/knowledgecenter/#!/was_beta_liberty/com.ibm.websphere.wlp.nd.multiplatform.doc/ae/twlp_sec_custmr.html
If you're looking for the solution of security domains provided in WAS Classic (the full profile), please open an RFE and be sure to vote for it!
https://www.ibm.com/developerworks/rfe/?BRAND_ID=181

Read-only access to Siteminder administration console

Is it possible to give someone access to the SiteMinder administration console, but in a read only fashion? We want some people to be able to see the configuration but not be able to modify anything.
SiteMinder Administrator accounts can be configured with fine-grained privileges that determine the administrative capabilities available to that administrator.
SiteMinder Administrator accounts are assigned rights to one or more security categories that define their administrative authority in the Administrative UI, such as managing authentication schemes. By default an Administrator account has access to every SiteMinder object related to an assigned security category.
Workspaces define a subset of SiteMinder objects. Assign a workspace to one or more Administrator accounts to filter the objects that are available to them, further controlling the scope of their administrative authority. An Administrator account whose authority is restricted by an assigned workspace is known as a scoped administrator.
Consult the SiteMinder Policy Server Configuration guide for more details...

Resources