GeoServer/web-security-core — Portuguese (Brazil) @ OSGeo Weblate: <p>Add, edit and remove individual chains</p><p>Different authentication mechanisms are available …

Translation

Key AuthenticationPage.authChainsHelp

English

Portuguese (Brazil)

Needs editing

Skip

Key	English	Portuguese (Brazil)
AuthenticationPage.bruteForceSettings	Brute force attack prevention settings
AuthenticationPage.bfMinDelaySeconds	Minimum delay on failed authentication (seconds)
AuthenticationPage.bfMaxDelaySeconds	Maximum delay on failed authentication (seconds)
AuthenticationPage.bfInvalidMinMax	Invalid min/max delay fields, maximum must be greater or equal than minimum
AuthenticationPage.bfMaxBlockedThreads	Maximum number of threads blocked on failed login delay
AuthenticationPage.bfWhitelistedNetmasks	Excluded network masks (comma separated)
AuthenticationPage.invalidMask	Invalid network mask '{0}'
AuthenticationPage.authFilters	Authentication Filters	Authentication Filters
AuthenticationPage.authFiltersHelp.title	Authentication Filters	Authentication Filters
AuthenticationPage.authFiltersHelp	<p>Authentication filters provide a method or mechanism for authentication and fall into two main categories:<ol><li>Filters that gather and process authentication information</li><li>Filters that do actual authentication</li></ol></p><p>The first category of filters are meant to be used in conjunction with an authentication provider. In this scenario the filter acts as a pre-processor whose job is to simply gather security credentials and it is the job of the provider to actually perform the authentication. An example is HTTP basic authentication in which the filter processes the HTTP basic auth header, extracting the username and password. Those credentials are then later processed by the provider to perform the actual authentication of the user.</p><p>The second category of filters are typically used in situations where authentication happens externally and are referred to as "pre-authentication" filters. Such filters recognize and process information from a pre-authentication and allow a request to proceed as authenticated. This category of filter does not require an authentication provider since the authentication has already taken place. An example would be a system that uses Siteminder for authentication, passing through the authenticated username in a request header.</p>	<p>Authentication filters provide a method or mechanism for authentication and fall into two main categories: <ol> <li>Filters that gather and process authentication information</li> <li>Filters that do actual authentication</li> </ol> </p> <p> The first category of filters are meant to be used in conjunction with an authentication provider. In this scenario the filter acts as a pre-processor whose job is to simply gather security credentials and it is the job of the provider to actually perform the authentication. An example is HTTP basic authentication in which the filter processes the HTTP basic auth header, extracting the username and password. Those credentials are then later processed by the provider to perform the actual authentication of the user.</p> <p>The second category of filters are typically used in situations where authentication happens externally and are referred to as "pre-authentication" filters. Such filters recognize and process information from a pre-authentication and allow a request to proceed as authenticated. This category of filter does not require an authentication provider since the authentication has already taken place. An example would be a system that uses Siteminder for authentication, passing through the authenticated username in a request header. </p>
AuthenticationPage.authProviders	Authentication Providers	Authentication Providers
AuthenticationPage.authProvidersHelp.title	Authentication Providers	Authentication Providers
AuthenticationPage.authProvidersHelp	<p>Authentication providers are the mechanism through which a a user is authenticated using some pre-defined authentication method.</p>	<p>Authentication providers are the mechanism through which a a user is authenticated using some pre-defined authentication method.</p>
AuthenticationPage.authChains	Filter Chains	Correntes de Filtros
AuthenticationPage.authChainsHelp.title	Filter Authentication Chains	Filtro de Correntes de Autenticação
AuthenticationPage.authChainsHelp	<p>Add, edit and remove individual chains</p><p>Different authentication mechanisms are available for each chain type. HTML chains should be used for chains returning HTML pages, service chains for all other kind of services.</p> <p>The order of the filter chains is important. The first chain matching an incoming request processes the request.</p>	<p>Adicionar, Editar e Remover correntes individuais</p><p>Diferentes mecanismos de autenticação estão disponíveis para cada tipo de corrente. Correntes HTML devem ser utilizadas para correntes retornando páginas HTML, correntes de serviços para todos os outros tipos de serviços.</p> <p>A ordem do filtro de corrente é importante. A primeira corrente corresponde a um processo de requisição de entrada.</p>
AuthenticationPage.filterChain	Filter chain testing	Filter Chains
AuthenticationPage.filterChainHelp.title	Filter testing	Filter Authentication Chain
AuthenticationPage.filterChainHelp	<p>Chain testing is done by specifying an HTTP method and the URL path excluding the context root. As an example, for testing <strong>http://localhost:8080/geoserver/wms?request=getCapabilities</strong> the test URL path is <strong>/wms</strong></p>	<p>A filter chain defines the order in which authentication filters are processed. The contents of a filter chain is specific to a particular type of request. For instance the filter chain for a web admin request is different than the filter chain for an OGC or REST service request.</p>
AuthenticationPage.httpMethod	HTTP method for testing	Método HTTP para teste
AuthenticationPage.urlPath	URL path for testing	URL para teste
AuthenticationPage.chainTestResult	Responsible chain	Corrente responsável
AuthenticationPage.chainTest	Find chain	Encontrar corrent
AuthenticationPage.providerChain	Provider Chain	Provider Chain
AuthenticationPage.providerChainHelp.title	Provider Authentication Chain	Provider Authentication Chain
AuthenticationPage.providerChainHelp	<p>The GeoServer authentication chain defines the order in which authentication providers are applied to a request in order to authenticate a user. Upon an incoming request, each provider in the chain is processed in order and given a chance to authenticate. Each provider may do one of three things:<ol><li>Signal a successful authentication if the user specified good credentials. When a successful authentication occurs chain processing is stopped.</li><li>Signal an unsuccessful authentication if the user specified bad credentials. When an unsuccessful authentication occurs chain processing is stopped.</li><li>Ignore the authentication request in cases where the provider does not apply to the method of authentication. For example if HTTP digest authentication is being used a basic username password authentication provider would simply ignore it. In this case the authentication chain processing continues to the next provider in the chain.</li></ol></p><p>If no provider in the chain is capable of authenticating the request an error (usually a 401) is sent back to the user.</p>	<p>The GeoServer authentication chain defines the order in which authentication providers are applied to a request in order to authenticate a user. Upon an incoming request, each provider in the chain is processed in order and given a chance to authenticate. Each provider may do one of three things: <ol> <li>Signal a successful authentication if the user specified good credentials. When a successful authentication occurs chain processing is stopped.</li> <li>Signal an unsuccessful authentication if the user specified bad credentials. When an unsuccessful authentication occurs chain processing is stopped.</li> <li>Ignore the authentication request in cases where the provider does not apply to the method of authentication. For example if HTTP digest authentication is being used a basic username password authentication provider would simply ignore it. In this case the authentication chain processing continues to the next provider in the chain.</li> </ol> </p> <p> If no provider in the chain is capable of authenticating the request an error (usually a 401) is sent back to the user.</p>
AuthenticationPage.requestChain	Request Chain	Request Chain
SecurityFilterChainPage.title	Filter chain	Filtrar corrent
SecurityFilterChainPage.description	Configure an individual filter chain	Configurar um filtro de corrente individual
SecurityFilterChainPage.name	Name	Nome
SecurityFilterChainPage.disabled	Disable security for this chain	Desabilitar segurança para esta corrente

Key	English	Portuguese (Brazil)
AbstractUserPage.groups	Groups	Grupos
AbstractUserPage.noAdminGroups	Group administrator role assigned but no groups selected	Group administrator role assigned but no groups selected
AbstractUserPage.password	Password	Senha
AbstractUserPage.passwordMismatch	Password and password confirmation are different	Password and password confirmation are different
AbstractUserPage.properties	User properties	User properties
AbstractUserPage.saveError	An error occurred while saving the user: {0}	Ocorreu um erro ao salvar o usuário: {0}
AbstractUserPage.username	User name	Nome de usuário
AnonymousAuthFilterPanel.description	Authenticates anonymously performing no actual authentication	Authenticates anonymously performing no actual authentication
AnonymousAuthFilterPanel.short	Anonymous	Anonymous
AnonymousAuthFilterPanel.title	Anonymous Authentication	Anonymous Authentication
AuthFilterChainPalette.availableHeader	Available	Disponível
AuthFilterChainPalette.selectedHeader	Selected	Selecionado
AuthenticationChainPalette.availableHeader	Available	Disponível
AuthenticationChainPalette.selectedHeader	Selected	Selecionado
AuthenticationPage.authChains	Filter Chains	Correntes de Filtros
AuthenticationPage.authChainsHelp	<p>Add, edit and remove individual chains</p><p>Different authentication mechanisms are available for each chain type. HTML chains should be used for chains returning HTML pages, service chains for all other kind of services.</p> <p>The order of the filter chains is important. The first chain matching an incoming request processes the request.</p>	<p>Adicionar, Editar e Remover correntes individuais</p><p>Diferentes mecanismos de autenticação estão disponíveis para cada tipo de corrente. Correntes HTML devem ser utilizadas para correntes retornando páginas HTML, correntes de serviços para todos os outros tipos de serviços.</p> <p>A ordem do filtro de corrente é importante. A primeira corrente corresponde a um processo de requisição de entrada.</p>
AuthenticationPage.authChainsHelp.title	Filter Authentication Chains	Filtro de Correntes de Autenticação
AuthenticationPage.authFilters	Authentication Filters	Authentication Filters
AuthenticationPage.authFiltersHelp	<p>Authentication filters provide a method or mechanism for authentication and fall into two main categories:<ol><li>Filters that gather and process authentication information</li><li>Filters that do actual authentication</li></ol></p><p>The first category of filters are meant to be used in conjunction with an authentication provider. In this scenario the filter acts as a pre-processor whose job is to simply gather security credentials and it is the job of the provider to actually perform the authentication. An example is HTTP basic authentication in which the filter processes the HTTP basic auth header, extracting the username and password. Those credentials are then later processed by the provider to perform the actual authentication of the user.</p><p>The second category of filters are typically used in situations where authentication happens externally and are referred to as "pre-authentication" filters. Such filters recognize and process information from a pre-authentication and allow a request to proceed as authenticated. This category of filter does not require an authentication provider since the authentication has already taken place. An example would be a system that uses Siteminder for authentication, passing through the authenticated username in a request header.</p>	<p>Authentication filters provide a method or mechanism for authentication and fall into two main categories: <ol> <li>Filters that gather and process authentication information</li> <li>Filters that do actual authentication</li> </ol> </p> <p> The first category of filters are meant to be used in conjunction with an authentication provider. In this scenario the filter acts as a pre-processor whose job is to simply gather security credentials and it is the job of the provider to actually perform the authentication. An example is HTTP basic authentication in which the filter processes the HTTP basic auth header, extracting the username and password. Those credentials are then later processed by the provider to perform the actual authentication of the user.</p> <p>The second category of filters are typically used in situations where authentication happens externally and are referred to as "pre-authentication" filters. Such filters recognize and process information from a pre-authentication and allow a request to proceed as authenticated. This category of filter does not require an authentication provider since the authentication has already taken place. An example would be a system that uses Siteminder for authentication, passing through the authenticated username in a request header. </p>
AuthenticationPage.authFiltersHelp.title	Authentication Filters	Authentication Filters
AuthenticationPage.authProviders	Authentication Providers	Authentication Providers
AuthenticationPage.authProvidersHelp	<p>Authentication providers are the mechanism through which a a user is authenticated using some pre-defined authentication method.</p>	<p>Authentication providers are the mechanism through which a a user is authenticated using some pre-defined authentication method.</p>
AuthenticationPage.authProvidersHelp.title	Authentication Providers	Authentication Providers
AuthenticationPage.bfEnabled	Enabled	Habilitado
AuthenticationPage.bfInvalidMinMax	Invalid min/max delay fields, maximum must be greater or equal than minimum
AuthenticationPage.bfMaxBlockedThreads	Maximum number of threads blocked on failed login delay
AuthenticationPage.bfMaxDelaySeconds	Maximum delay on failed authentication (seconds)
AuthenticationPage.bfMinDelaySeconds	Minimum delay on failed authentication (seconds)
AuthenticationPage.bfWhitelistedNetmasks	Excluded network masks (comma separated)
AuthenticationPage.bruteForceSettings	Brute force attack prevention settings