Portal for ArcGIS may be configured for Enterprise logins (eg SAML/Active Directory). An organisation may require their Portal content to be managed based on Active Directory Group membership. The below answers the question “Does Portal automatically create groups to match Active Directory Groups and will users automatically be added to these groups when first logging in to Portal using their Enterprise Logins?”
The answer is yes, we simply need to configure portal groups and bind them to the active directory group using the below steps.
Does Portal inherit Active Directory Configured Membership groups?
Portal for ArcGIS does not automatically create groups to match what is available in Active Directory. The GIS Administrator will need to create and configure groups in Portal for ArcGIS for each of the Active Directory Groups that they want to allow membership of.
How to configure Portal to enable Enterprise Group Membership
User will need to Manually create the Portal Groups then bind them to the Active Directory Group
First, configure the organisation SAML settings to enable SAML based Group Membership. This may be done via Organisations > Settings > Security > Logins > Configure > Advanced Settings
You will then have the ability to create Portal groups with the setting “Enable SAML based group membership”
Here is where you will need to configure the enterprise group name. This name may not be a recognisable name, it may be a group ID or SID. Members will only be added to the group once they have logged in and if there is a group in the SAML assertion response which matches the enterprise group name.
Can SAML/Active Directory users be automatically added to configured Enterprise groups when signing into Portal?
Yes. Once you have configured the Portal Groups and associated them with their respective Active Directory groups you do not need to manage membership of those groups within Portal. When a user logs in with their enterprise account, the groups to which they are members in Active Directory is returned in the SAML response and ArcGIS reflects that by allowing the user membership to the matching groups you have defined.
ArcGIS GeoBIM licenses are currently an inclusion of ArcGIS Online ArcGIS Professional Standard and ArcGIS Professional Advanced user types. You can read more on user types here.
If your organization does not have an ArcGIS Professional Standard or Advanced user type, GeoBIM can be purchased as an add-in license and then assigned to a compatible User Type, within your ArcGIS Online subscription. You can see more on how to manage licenses here.
If you would like to learn more about GeoBIM, please feel free to contact us
Data published as a feature layer must reference a single source geodatabase or database. You cannot publish data from more than one database connection in a single map.
In ArcGIS Pro, if you were to publish the data in a map as a map image and feature layer and there are multiple data sources referenced in the map you will get an error: ‘00062: Map contains data that does not use the same connection to an enterprise geodatabase’.
Web feature layers associated with a map image layer require that all layers and stand-alone tables in the service reference an enterprise geodatabase or a standard enterprise database using a single connection.
Data published only as a map service can come from multiple data sources. While it is possible to enable feature access on a map service after publishing, only the layers from a single data source referenced by the feature service would be accessible.
With almost any Portal there comes a time when you have dozens of items, created over time by different people, and you may be looking to perform a bit of a clean-up.
The problem now arises that you do not know if the Web Map made by a colleague, who since left the organisation, can be deleted or if it is being used by any other items? You might find that deleting an insignificant-looking item brings your organisation’s most-used application down.
Question What is the correct workflow to achieve a full compress in a versioned geodatabase using replicas?
Answer To achieve a full compress in a versioned geodatabase (that is, move edits from the Adds and Deletes tables to the business tables, and remove unreferenced states), perform the following workflow:
As your ArcGIS Online organization grows, so does the amount of content, and subsequently the credit consumption to store it. It is important for Creators to understand which types of items consume storage credits at a higher rate, and for administrators to identify which users and items are incurring the highest usage.
As the administrator of an ArcGIS Online organization, you have the ability to review your organization’s subscription details and credit status, manage members and licenses, monitor activity, generate usage reports and configure settings. Understanding and managing your organization’s credits may be new to you; but there is a wealth of resources available to help you navigate this task.
This article aims to provide you with a step-by-step guide of these key resources, to point you in the right direction, and ultimately get you started with managing credits in ArcGIS Online.
Esri Australia has been working with Esri and ICSM to ensure that the ArcGIS system can support clients migration from the GDA94 static datum to GDA2020 static datum. The ArcGIS system now fully supports data transformations via 7-parameter similarity transformation, or NTv2.0 transformation Grids.
As a result we are now seeing many clients migrate their authoritative datasets to GDA2020 and requiring all delivered data is in this same static datum. State and national governments are now delivering foundational open datasets in GDA2020 as well
In parallel to this migration we are also seeing more clients taking up WebGIS and delivering data via web services instead of shipping datasets or producing PDF’s. This is enabling a greater uptake web and mobile GIS, providing better informed field operators and getting live data in the hands of people who need it as they need it.
These two waves of change have presented a significant challenge. While transformations existed between WGS84 & GDA94 and GDA94 & GDA2020, there existed no direct path from GDA2020 to WGS84. If you wanted to place GDA2020 data into WebGIS you had to transform you data back through GDA94 to WGS84. Effectively moving the data back to its old location prior to publishing. Many clients asked why????
It has been termed the WGS84 Projection dilemma. So what’s changing?